Temporary expanding integrated monitoring network

ABSTRACT

A system for monitoring an industrial process and taking action based on the results of process monitoring. Actions taken may include process control, paging, voicemail, and input for e-enterprise systems. The system includes an input module for receiving a plurality of parameters from a process for manufacture of a substance or object. The system also includes a library module. The library module includes a plurality of computer aided processes. Any one of the computer aided processes is capable of using each of the plurality of parameters to compare at least two of the plurality of parameters against a training set of parameters. The training set of parameters is generally predetermined. The computer aided process is also capable of determining if the at least two of the plurality of parameters are within a predetermined range of the training set of parameters. Additionally, the system includes an output module for outputting a result based upon the training set and the plurality of parameters.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional application of U.S. patent applicationSer. No. 10/214,631, filed Aug. 7, 2002, now U.S. Pat. No. 7,031,778,which is a continuation application of U.S. patent application Ser. No.09/802,377, filed Mar. 9, 2001, now U.S. Pat. No. 6,835,920, which alsoclaims the benefit of the following three provisional patentapplications, each filed Mar. 10, 2000 and incorporated herein byreference: U.S. provisional patent application No. 60/188,565; U.S.provisional patent application No. 60/188,590; and U.S. provisionalpatent application No. 60/188,591. The following nonprovisional patentapplications are hereby incorporated by reference: U.S. nonprovisionalpatent application Ser. No. 09/802,519; and U.S. nonprovisional patentapplication Ser. No. 09/802,512.

BACKGROUND OF THE INVENTION

This invention in general relates to processing information or data overa network of computers. Embodiments of the present invention relate totechniques for monitoring and/or controlling complex processes bycomparing the current state of a first process to current, historical,and/or predicted states of the first process or a second process usingstatistical, structural, or physical models. Other embodiments of thepresent invention provide a system including computer code formonitoring or controlling, or both monitoring and controlling a processusing multi-dimensional data in a commercial setting. Themultidimensional data can include, among others, intrinsic informationsuch as temperature, acidity, chemical composition, and color, as wellas extrinsic information, such as origin, and age. The multidimensionaldata can also include symbolic data that is primarily visual in natureand which does not readily lend itself to traditional quantification.Merely by way of example, the present invention is described below inconjunction with an industrial manufacturing process, but it would berecognized that the invention has a much broader range of applicability.The invention can be applied to monitor and control complex processes inother fields such as chemicals, electronics, biological, health care,petrochemical, gaming, hotel, commerce, machining, electrical grids, andthe like. Embodiments of the present invention may further accomplishprocess control in real time utilizing a web-based architecture.

Techniques and devices for maintaining process control in complexprocesses are well known. Such techniques often require monitoringindividual parameters such as temperature, pressure, flow, incomingfluid characteristics, and the like. Most of these techniques onlymonitor and adjust a single parameter. The single parameter is oftenmonitored and displayed to an operator or user of the process through anelectronic display. For example, refining a petroleum product such asoil or gas often uses temperature measurements of raw or in processfluids such as oil using thermocouples. These thermocouples are oftenattached to critical processes such as distillation and the like andthen coupled to an electronic display for output. The display generallyoutputs signals corresponding to temperature in a graphical userinterface form or numerical value in Celsius, for example. In the mostprimitive oil refining operations, for example, operators still monitortemperature of a process or processes using the display by visual means.If the temperature goes out of range, the operator merely adjusts theprocess. In more advanced applications, process controllers monitor andcontrol temperature of processes. The process controllers often useproportional control, derivative control, integral control, or acombination of these to provide an optimum control of temperature forthe process. These techniques, however, still only monitor in singleparameter such as temperature and adjust-such temperature by feedbackcontrol means.

Oil refining is merely one of many examples of industrial processes thatrequire control. Other examples include food processing, chemicalproduction, drug manufacturing, semiconductor processing, watertreatment, agriculture, assembly operations, health care, electronicpower, gaming, hotel, and other commerce related fields. All of theseexamples generally use fairly crude processing techniques for adjustingcomplex processing variables such as temperature, pressure, flow rate,speed, and others, one at a time using automatic feed back control ormanual feed back control. In some applications, fairly complex sensorassemblies are used to monitor process parameters. U.S. Pat. No.5,774,374 in the name of Gross et al. and assigned to the University ofChicago, describes one way of monitoring an industrial or biologicalprocess using sensors. This conventional approach relies upon comparinga measured signal against a reference signal by subjective criteria.However, the subjective criteria have often been determined by trial anderror and are only as good as the person deciding upon such criteria.

Many limitations still exist with some or all of these techniques. Forexample, most of these techniques still only monitor a single parameterand adjust it against a subjective reference point. Human monitoring ofmultiple parameters is often required, which is only as good as thehuman operator. Additionally, many if not all of these techniques cannotmonitor the quality of a substance in process. Here, only extrinsicvariables such as temperature, pressure, and the like can be easilymonitored. There is simply no easy way to monitor the substance itselfwhile it is being processed. Although complex chemical analysis methodsare available to determine specific components or weights of thesubstance, there is simply no easy way to identify the quality of thesubstances while it is being manufactured. These and many otherlimitations are described throughout the present specification and moreparticularly below.

From the above, it is seen that improved ways of monitoring orcontrolling a process, or both monitoring and controlling a process, arehighly desirable.

SUMMARY OF THE INVENTION

According to the present invention, a technique for processinginformation or data over a network of computers is provided, including asystem for monitoring or controlling a process, or both monitoring andcontrolling a process. Embodiments of the present invention provide asystem including computer codes for process monitoring and/or controlusing multidimensional data. The multidimensional data can include,among others, intrinsic information such as temperature, acidity,chemical composition, and color, as well as extrinsic information suchas origin, and age.

In accordance with embodiments of the present invention, a process maybe monitored and/or controlled by comparing the current state of a firstprocess to current, historical, and/or predicted states of the firstprocess or of a second process through the use of statistical,structural, or physical models. The process is then monitored and/orcontrolled based upon a descriptor predicted by the model. For purposesof this application, the term “descriptor” includes modelcoefficients/parameters, loadings, weightings, and labels, in additionto other types of information.

In one specific embodiment of a system for controlling a process, thesystem comprises a computer program product comprising a code directedto storing a first model in memory, a code directed to acquiring datafrom a process, and a code directed to applying the first model to thedata to identify a first predicted descriptor characteristic of a stateof the process. A code is directed to consulting a first knowledge basedsystem to provide an output based upon the first predicted descriptor.

In another embodiment of a system for controlling an industrial process,the system includes a computer program product. The product includescode directed to accessing a process controller. The product alsoincludes code directed to an input module adapted to input a pluralityof parameters from a process. The product also includes code directed toa computer aided process module coupled to the process controller, thecomputer aided process module code being adapted to compare at least twoof the plurality of parameters against a predetermined training set ofparameters, and being adapted to determine if the least two of theplurality of parameters are within a predetermined range of the trainingset of parameters. Additionally, the product includes code directed toan output module for outputting a result based upon the training set andthe plurality of parameters. Other functionality described herein canalso be implemented in computer code and the like according to otherembodiments of the present invention.

In another embodiment of a system for controlling a process, the systemcomprises a first field mounted device in communication with a processand configured to produce a first input. A process manager receives thefirst input and is configured to -apply a first model to the first inputto identify a first predicted descriptor characteristic of a state ofthe process. The process manager is further configured to consult afirst knowledge based system to provide an output based upon the firstpredicted descriptor.

In one embodiment of a method for controlling a process, the methodcomprises storing a first model in a memory and acquiring data from aprocess. The first model is applied to the data to identify a firstpredicted descriptor characteristic of a state of the process, and afirst knowledge based system is consulted to provide an output basedupon the first predicted descriptor.

Numerous benefits are achieved by way of the present invention overconventional techniques. For example, because of its web-basedarchitecture, embodiments of the present invention permit monitoringand/or control over a process to be performed by a user locatedvirtually anywhere. Additionally, embodiments of the invention permitmonitoring and control over a process in real time, such thatinformation about the process can rapidly be analyzed by a variety oftechniques, with corrective steps based upon the analysis implementedimmediately. Further, because the invention utilizes a plurality ofanalytical techniques in parallel, the results of these analyticaltechniques can be cross-validated, enhancing the reliability andaccuracy of the resulting process monitoring or control. The presentinvention can be used with a wide variety of processes, e.g., thoseutilized in the chemical, biological, petrochemical, and foodindustries. However, the present invention is not limited to controllingthe process of any particular industry, and is generally applicable tocontrol over any process. Depending upon the embodiment, one or more ofthese benefits may be achieved. These and other benefits will bedescribed in more detail throughout the present specification and moreparticularly below.

Various additional objects, features and advantages of the presentinvention can be more fully appreciated with reference to the detaileddescription and accompanying drawings that follow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified diagram of an environmental information analysissystem according to an embodiment of the present invention;

FIG. 1A is a simplified block diagram showing a process monitoring andcontrol system in accordance with one embodiment of the presentinvention.

FIGS. 2 to 2A are simplified diagrams of computing device for processinginformation according to an embodiment of the present invention;

FIG. 3 is a simplified diagram of computing modules for processinginformation according to an embodiment of the present invention;

FIG. 3A is a simplified diagram showing interaction between a processmanager and various analytical techniques available to monitor aprocess.

FIG. 3B is a simplified diagram of a capturing device for processinginformation according to an embodiment of the present invention; and

FIGS. 4A to 4E are simplified diagrams of methods according toembodiments of the present invention.

FIG. 5 is a chart showing users of the Software.

DETAILED DESCRIPTION OF THE INVENTION AND SPECIFIC EMBODIMENTS

The present invention relates to processing information or data over anetwork of computers. More specifically, embodiments of the presentinvention include methods, systems, and computer code for monitoring orcontrolling a process, or for both monitoring and controlling a process.

FIG. 1 is a simplified diagram of an integrated computer aided system100 for monitoring and controlling a process according to an embodimentof the present invention. This diagram is merely an example which shouldnot limit the scope of the claims herein. One of ordinary skill in theart would recognize many other variations, modifications, andalternatives.

As shown, system 100 includes a variety of sub-systems that areintegrated and coupled with one another through a web-basedarchitecture. One example of such a sub-system is wide area network 109which may comprise, for example, the Internet, an intranet, or anothertype of network. The Internet is shown symbolically as a cloud or acollection of server routers, computers, and other devices.

As used in this patent application and in industry, the concepts of“client” and “server,” as used in this application and the industry, arevery loosely defined and, in fact, are not fixed with respect tomachines or software processes executing on the machines. Typically, aserver is a machine e.g. or process that is providing information toanother machine or process, i.e., the “client,” e.g., that requests theinformation. In this respect, a computer or process can be acting as aclient at one point in time (because it is requesting information) andcan be acting as a server at another point in time (because it isproviding information). Some computers are consistently referred to as“servers” because they usually act as a repository for a large amount ofinformation that is often requested. For example, a website is oftenhosted by a server computer with a large storage capacity, high-speedprocessor and Internet link having the ability to handle manyhigh-bandwidth communication lines.

Wide area network 109 allows for communication with other computers suchas a client unit 112. Client 112 can be configured with many differenthardware components and can be made in many dimensions, styles andlocations (e.g., laptop, palmtop, pen, server, workstation andmainframe).

Server 113 is coupled to the Internet 109. The connection between server113 and internet 109 is typically by a relatively high bandwidthtransmission medium such as a T1 or T3 line, but can also be othermedia, including wireless communication. Terminal 102 is also connectedto server 113. This connection can be by a network such as Ethernet,asynchronous transfer mode, IEEE standard 1553 bus, modem connection,universal serial bus, etc. The communication link need not be in theform of a wire, and could also be wireless utilizing infrared, radiowave transmission, etc.

Another subsystem of system 100 of FIG. 1 are the various field mounteddevices 105 in contact with process 121 located in plant 122. While FIG.1 does illustrate process monitoring/control in conjunction with anindustrial process, the present invention is not limited to such anapplication. Other types of complex processes, such as medicaldiagnostic procedures, could also be monitored and/or controlled inaccordance with embodiments of the present invention.

Field mounted devices 105 can include sensors, transmitters, actuators,multifunctional devices, or Remote Terminal Units (RTU's), among others.As shown in FIG. 1, field mounted devices 105 may be controlled by adevice such as a programmable logic controller (PLC) 115. Field mounteddevices 105 are generally coupled to a central Supervisory Control andData Acquisition (SCADA) system 129. SCADA system 129 enables control,analysis, monitoring, storage and management of the information flowbetween the systems at the field level and at the control level of acompany. This ensures that the decentralized I/O modules and the machinecontrollers are linked to the office computers on the control level.Components of control, analysis, monitoring. A particular process mayutilize more than one SCADA system at a time.

FIG. 1 also shows that a field mounted device 105 may be linked directlywith internet 109, bypassing SCADA 129 and other common interfacesaltogether. Such an arrangement will become increasingly prevalent asthe use of web-enabled devices (devices including devotedhardware/software interfaces) increases. And while FIG. 1 showswire-based direct communication between a field mounted device and theinternet, such web-enabled devices may alternatively communicatedirectly with the internet through wireless technology.

FIG. 1 further shows that a field mounted device 105 may be coupled to alaptop client computer 112 that is in turn in communication withinternet 109. This latter configuration is particularly useful where aparticular field mounted device is not permanently linked to the processvia SCADA system 129, but is instead transported to process 121 andtemporarily installed by technician 111 for specialized diagnostic orcontrol purposes.

Field mounted devices 105 can be similar or can also be different,depending upon the application. One example of a field mounted device isa sensing element for acquiring olfactory information from fluidsubstances, e.g., liquid, vapor, liquid/vapor. Once the information isacquired by field mounted device 105, device 105 may transferinformation to server 113 for processing purposes. In one aspect of thepresent invention, process 121 is monitored and controlled usinginformation that includes multi-dimensional data. Details of theprocessing hardware is shown below and illustrated by the Figs.

Database 106 is connected to server 113. Database 106 includesinformation useful for process control and monitoring functions. Forexample, database 106 may store information regarding process 121received from field mounted devices 105. Database 106 may also include alibrary of different algorithms or models that may be used to monitorand control industrial process 121. Alternatively, such a library ofalgorithms or models may be resident on server 113.

In accordance with embodiments of the present invention, the outcome ofapplying a specific algorithm or model to process 121 may be internallycross-validated by comparing the result application of other algorithmsor models to the same data. Examples of specific algorithms and models,and their role in process control/monitoring methods and systems inaccordance with embodiments of the present invention, are described morefully below.

FIG. 1 also shows that internet 109 is linked to one or more externalsystems 125. Examples of such external systems include EnterpriseResource Planning (ERP) systems and Lab Information Management Systems(LIMS). External system 125 could also be a duplicate or sister processof process 121, such that the state of process 121 may be externallyvalidated by comparison with the results of the second process.

FIG. 1A is a simplified block diagram showing a process monitoring andcontrol system in accordance with one embodiment of the presentinvention. FIG. 1A shows various layers where information is gathered,distributed, and/or processed.

Bottom portion 150 of FIG. 1A represents structures that are in generallocated proximate to the physical location of the process itself, suchas in the manufacturing plant. The lowest layer of portion 150represents field mounted devices 105 such as RTU's, sensors, actuators,and multifunctional devices in direct contact with the process. The nextlayer represents logic devices 115 such as programmable logiccontrollers (PLC) that receive signals from and transmit signals to,field mounted devices 105. The next layer of FIG. 1A representscommunication structures 152 such as buses, wide area networks (WAN), orlocal area networks (LAN) that enable communication using TCP/IPprotocols of data collected by field mounted devices 105 to acentralized location. This centralized location is represented by thenext layer as Structured Query Language (SQL) or OPC (OLE for ProcessControl, where OLE is Object Linking and Embedding) server 154. Server154 includes an interface with database 156, used for example to storearchived process data, and also typically includes a user interface 158.The user interface can be a direct human machine interface (HMI), or aspreviously described can take the form of a SCADA system.

Field mounted devices 105, logic devices 115, communication structures152, and server 154 are each in communication with hardware interface160 that is in turn in communication with software interface 162.Software interface 162 links bottom portion 150 of FIG. 1A with middleportion 165 of FIG. 1A.

Middle portion 165 represents process control and monitoring processesin accordance with embodiments of the present invention. An input moduleincludes software interface 162 which couples information from theconventional processing plant to a plurality of processes for operationsand analysis. As known to those of skill in the art, the softwareinterface 162 may take the form of several standards, including OpenDataBase Connectivity (ODBC), or Dynamic Data Exchange (DDE) standards.Software interface 162 in turn couples with server 166, rendering bothinputs and outputs of the process control system accessible viaweb-based communication. Specifically, data from the process may beacquired over the internet, and outputs from the system may be accessedby a user over the internet utilizing browser software.

In the next layer 167, data received by server 166 is synchronized topermit orderly assimilation for monitoring and control purposes. In thenext layer 168, the assimilated data is examined and manipulated using a-variety of techniques, including statistical/numerical algorithms andtools 168, expert systems 170, and others. These processes also includemodel building 176 to accurately predict behavior of the process, andmodel monitoring 178 based upon inputs received from the plant.

Common interface 172 is part of an output module that couples theanalysis processes of middle portion 165 with selected legacy systemsshown in top portion 180 of FIG. 1A. Such legacy systems includedatabases 182, display systems 184 for sounds/alarms, and desktopapplications 185. Legacy systems may also include Enterprise ResourcePlanning (ERP) and other e-enterprise systems 186, as well as SupplyChain Management (SCM) systems. The legacy systems may further includeequation-based models 188 for predicting process behavior based uponphysical laws.

FIG. 1A illustrates several aspects of process monitoring and/or controlin accordance with embodiments of the present invention. For example,process modeling and control may be implemented utilizing a web-basedarchitecture. Statistical methods, expert systems, and algorithmsutilized to monitor and control the process need not be present at theplant site, but rather can receive information from the plant over theweb. This allows the user to monitor and control process parameters fromessentially any physical location, particularly given the emergence ofwireless communications.

In certain embodiments of systems in accordance with the presentinvention, algorithms and models, and the results of application ofalgorithms and models to process data, may all be resident or accessiblethrough a common application server. In this manner, the user mayremotely access data and/or model results of interest, carefullycontrolling the bandwidth of information transmitted communicatedaccording to available communication hardware. This server-basedapproach simplifies access by requiring user access to a simple browserrather than a specialized software package.

Yet another aspect of the present invention is the ability to monitorand control a process in real time. Specifically, data collected by thefield level-sensors may rapidly be communicated over the Internet to theserver that is coordinating application of statistical methods, expertsystems, and algorithms in accordance with embodiments of the presentinvention. These techniques can rapidly be applied to the data toproduce an accurate view of the process and to provide recommendationsfor user action.

Still another aspect of the present invention illustrated in FIG. 1A isthe ability to precisely dictate the autonomy of process monitoringand/or control from human oversight. Specifically, the system permitsscalable autonomy of process monitoring and control from a human user.On one end of the scale, a human user can have an intimate role with thesystem, carefully monitoring incoming process data, viewing possibleinterpretations of the data based upon models, expert systems, andalgorithms, and then based upon these possible interpretations selectinga course of action based upon his or her experience, intuition, andjudgment. Alternatively, the role of the human user can be lessintimate, with the human operator merely monitoring the responsesundertaken by the system to control the process, and focusing uponprocess control only in unusual situations or even not at all.

Another aspect of the present invention is the ability to rapidly andeffectively transfer key preliminary information downstream to processmonitoring and modeling functions. For example, the present inventionmay be utilized to monitor and control an oil refining process. Keyoperational parameters in such a process would be affected bypreliminary information such as the physical properties of incoming lotsof crude oil starting material. One example of a test for measuring thephysical properties of crude oil is American Society for Testing andMaterials (ASTM) method number 2878, in which 22 temperatures aremeasured after specified amounts of fluids have been vaporized. Thevalues of these 22 variables from lot-to-lot are likely to providesufficient information to calculate appropriate set point values for oneor more temperatures in a petroleum cracking process, such as thetemperature profile for the first in a series of reactors.

Utilizing the present invention, the crude oil could be sampled andanalyzed using the ASTM 2878 method at a location distant from therefinery (i.e. at the oil field or on a ship approaching the refinery),and data from the analysis communicated in real time over a web-basedlink downstream to the process monitoring and control functionalities.Process monitoring and control functionalities (i.e. models, algorithms,and/or knowledge based systems) could be adjusted to take into accountthe specific properties of the incoming crude oil, ensuring the accuracyand reliability of the determination of process state.

Another aspect of the present invention is parallel use of a widevariety of techniques for process monitoring and control, with enhancedreliability obtained by cross-validating results of these techniques.This aspect is further illustrated in connection with FIGS. 2-3A.

FIG. 2 is a simplified diagram of a computing device for processinginformation according to an embodiment of the present invention. Thisdiagram is merely an example which should not limit the scope of theclaims herein. One of ordinary skill in the art would recognize manyother variations, modifications, and alternatives. Embodiments accordingto the present invention can be implemented in a single applicationprogram such as a browser, or can be implemented as multiple programs ina distributed computing environment, such as a workstation, personalcomputer or a remote terminal in a client server relationship.

FIG. 2 shows computer system 210 including display device 220, displayscreen 230, cabinet 240, keyboard 250, and mouse 270. Mouse 270 andkeyboard 250 are representative “user input devices.” Mouse 270 includesbuttons 280 for selection of buttons on a graphical user interfacedevice. Other examples of user input devices are a touch screen, lightpen, track ball, data glove, microphone, and so forth. FIG. 2 isrepresentative of but one type of system for embodying the presentinvention. It will be readily apparent to one of ordinary skill in theart that many system types and configurations are suitable for use inconjunction with the present invention. In a preferred embodiment,computer system 210 includes a Pentium™ class based computer, runningWindows™ operating system by Microsoft Corporation. However, theapparatus is easily adapted to other operating systems and architecturesby those of ordinary skill in the art without departing from the scopeof the present invention.

As noted, mouse 270 can have one or more buttons such as buttons 280.Cabinet 240 houses familiar computer components such as disk drives, aprocessor, storage device, etc. Storage devices include, but are notlimited to, disk drives, magnetic tape, solid state memory, bubblememory, etc. Cabinet 240 can include additional hardware such asinput/output (I/O) interface cards for connecting computer system 210 toexternal devices external storage, other computers or additionalperipherals, which are further described below.

FIG. 2A is an illustration of basic subsystems in computer system 210 ofFIG. 2. This diagram is merely an illustration and should not limit thescope of the claims herein. One of ordinary skill in the art willrecognize other variations, modifications, and alternatives. In certainembodiments, the subsystems are interconnected via a system bus 275.Additional subsystems such as a printer 274, keyboard 278, fixed disk279, monitor 276, which is coupled to display adapter 282, and othersare shown. Peripherals and input/output (I/O) devices, which couple toI/O controller 271, can be connected to the computer system by anynumber of means known in the art, such as serial port 277. For example,serial port 277 can be used to connect the computer system to a modem281, which in turn connects to a wide area network such as the Internet,a mouse input device, or a scanner. The interconnection via system busallows central processor 273 to communicate with each subsystem and tocontrol the execution of instructions from system memory 272 or thefixed disk 279, as well as the exchange of information betweensubsystems. Other arrangements of subsystems and interconnections arereadily achievable by those of ordinary skill in the art. System memory,and the fixed disk are examples of tangible media for storage ofcomputer programs, other types of tangible media include floppy disks,removable hard disks, optical storage media such as CD-ROMS and barcodes, and semiconductor memories such as flash memory,read-only-memories (ROM), and battery backed memory.

FIG. 3 is a simplified diagram of computing modules 300 in a system forprocessing information according to an embodiment of the presentinvention. This diagram is merely an example which should not limit thescope of the claims herein. One of ordinary skill in the art wouldrecognize many other variations, modifications, and alternatives. Asshown, the computing modules 300 include a variety of processes, whichcouple to a process manager 314. The processes include an upload process301, a filter process 302, a base line process 305, a normalizationprocess 307, a pattern process 309, and an output process 311. Otherprocesses can also be included. A non-exclusive explanatory list ofpre-processing techniques utilized by the present invention is given inTABLE 7.

Process manager also couples to data storage device 333 and oversees theprocesses. These processes can be implemented in software, hardware,firmware, or any combination of these in any one of the hardwaredevices, which were described above, as well as others.

The upload process takes data from the acquisition device and uploadsthem into the main process manager 314 for processing. Here, the dataare in electronic form. In embodiments where the data has been- storedin data storage, they are retrieved and then loaded into the process.Preferably, the data can be loaded onto workspace to a text file orloaded into a spread sheet for analysis. Next, the filter process 302filters the data to remove any imperfections. As merely an example, datafrom the present data acquisition device are often accompanied withglitches, high frequency noise, and the like. Here, the signal to noiseratio is often an important consideration for pattern recognitionespecially when concentrations of analytes are low, exceedingly high, ornot within a predefined range of windows according to some embodiments.In such cases, it is desirable to boost the signal to noise ratio usingthe present digital filtering technology. Examples of such filteringtechnology includes, but is not limited to a Zero Phase Filter, anAdaptive Exponential Moving Average Filter, and a Savitzky-Golay Filter,which will be described in more detail below.

The data go through a baseline correction process 305. Depending uponthe embodiment, there can be many different ways to implement a baselinecorrection process. In the field of process control, one approach toestablishing a baseline is stationarization. Stationarization involvesthe elimination of seasonal and/or batch variations from process controlanalysis. Stationarization is particularly useful in monitoring the timedynamics of a process. In monitoring process dynamics, the value of asingle measurement, such as temperature, may not be as important as therelationship between successive temperature measurements in time.

A baseline correction process may also find response peaks, calculateΔR/R, and plot the ΔR/R verses time stamps, where the data have beencaptured. It also calculates maximum ΔR/R and maximum slope of ΔR/R forfurther processing. Baseline drift is often corrected by way of thepresent process. The main process manager also oversees that datatraverse through the normalization process 307. In some embodiments,normalization is a row wise operation. Here, the process uses aso-called area normalization. After such normalization method, the sumof data along each row is unity. Vector length normalization is alsoused, where the sum of data squared of each row equals unity.

Next, the method performs a main process for classifying each of thesubstances according to each of their characteristics in a patternrecognition process. The pattern recognition process uses more than onealgorithms, which are known, are presently being developed, or will bedeveloped in the future. The process is used to find weighting factorsfor each of the characteristics to ultimately determine an identifiablepattern to uniquely identify each of the substances. That is,descriptors are-provided for each of the substances. Examples of somealgorithms are described throughout the present specification. Alsoshown is the output module 311. The output module is coupled to theprocess manager. The output module provides for the output of data fromany one of the above processes as well as others. The output module canbe coupled to one of a plurality of output devices. These devicesinclude, among others, a printer, a display, and a network interfacecard. The present system can also include other modules. Depending uponthe embodiment, these and other modules can be used to implement themethods according to the present invention.

The above processes are merely illustrative. The processes can beperformed using computer software or hardware or a combination ofhardware and software. Any of the above processes can also be separatedor be combined, depending upon the embodiment. In some cases, theprocesses can also be changed in order without limiting the scope of theinvention claimed herein. One of ordinary skill in the art wouldrecognize many other variations, modifications, and alternatives.

FIG. 3A is a simplified view of the interaction between various processcontrol and monitoring techniques that may be employed in accordancewith embodiments of the present invention. This diagram is merely anexample which should not limit the scope of the claims herein. One ofordinary skill in the art would recognize many other variations,modifications, and alternatives.

As shown in FIG. 3A, server 161 receives raw process data from a plantvia a net-based software interface. Once the raw data has beenpre-processed, it is communicated to process manager 314. Processmanager 314 may in turn access a wide variety of techniques in order toanalyze and characterize the data received. Specifically, a model oralgorithm may be applied to the data to identify a predicted descriptorcharacteristic of a state of the process. A knowledge based system maythen be consulted to provide an output based upon the predicteddescriptor. This output may be utilized to monitor and control theprocess if desired.

As shown in FIG. 3A, process manager 314 is communication with database316 and with models 178 a and 178 b. Models 178 a and 178 b attempt tosimulate the behavior of the process being controlled, thereby allowingprediction of future behavior. A library of the different categories ofalgorithms used to form models can be stored in data storage device 333so as to be accessible to process manager 314. Models 178 a and 178 bmay be constructed upon a variety of fundamental principles.

One approach is to model the process based upon data received fromoperation of a similar process, which may or may not be located in thesame plant. This aspect of the present invention is particularlyattractive given the recent trend of standardizing industrial plants,particularly for newly-constructed batch processes. Such standardizedindustrial plants may feature identical equipment and/orinstrumentation, such that a model built to predict the behavior of oneplant can be used to evaluate the health of another plant. For example,the manager of a semiconductor fabrication plant in the United Statesmay compare operation of a particular type of tool with data from anidentical tool operating in a second semiconductor fabrication plantlocated in Malaysia. This comparison may occur in real time, or mayutilize archived data from past operation of the tool in the secondsemiconductor fabrication plant. Moreover, the processes or tools to becompared need not be identical, but may be similar enough thatcomparison between them will provide information probative of the stateof the process.

Another type of model may be based upon mathematical equations derivedfrom physical laws. Examples of such physical laws include mass balance,heat balance, energy balance, linear momentum balance, angular momentumbalance, entropy and a wide variety of other physical models. Themathematical expressions representing these physical laws may be storedin data storage device 333 so as to be accessible for process analysis.

Yet another type of model is based upon algorithms such as statisticaltechniques. A non-exclusive, explanatory list of univariate techniqueswhich may be utilized by the present invention is presented in TABLE 8.Another type of model is based upon multivariate statistical techniquessuch as principal component analysis (PCA). A non-exclusive, explanatorylist of multivariate techniques that may be utilized by the presentinvention is presented in TABLE 10. The appended software specificationalso provides details regarding both model building and model monitoringutilizing several of these multivariate techniques. Still other modeltypes may rely on a neural-based approach, examples of which include butare not limited to neural networks and genetic selection algorithms.

Other models may themselves be a collection of component models. Onesignificant example of this model type is the System Coherence RenderingException Analysis for Maintenance (SCREAM) model currently beingdeveloped by the Jet Propulsion Laboratory of Pasadena, Calif.Originally developed to monitor and control satellites, SCREAM is acollection of models that conduct time-series analysis to provideintelligence for system self-analysis. A detailed listing of thetechniques utilized by SCREAM is provided in TABLE 11.

One valuable aspect of SCREAM is recognition of process lifecycles. Manyprocess dynamics exhibit a characteristic life cycle. For example, agiven process may exhibit non-linear behavior in an opening stage,followed by more predictable linear or cyclical phases in a maturestage, and then conclude with a return to non-linear behavior in aconcluding stage. SCREAM is especially suited not only to recognizingthese expected process phases, but also to recognizing undesirabledeviation from these expected phases.

Another valuable aspect of SCREAM is the ability to receive and analyzesymbolic data. Symbolic data are typically data not in the form of ananalog signal, and hence not readily susceptible to quantitation.Examples of symbolic data typically include labels and digital/integerinputs or outputs. Symbolic data is generally visual in nature, forexample a position of a handle, a color of a smoke plume, or the-general demeanor of a patient (in the case of a medical diagnosticprocess).

SCREAM uses symbolic inputs to determine the state of the process. Forexample, positions of on/off valves may be communicated as a digitalsignal using ‘0’ to represent the open position and ‘1’ to represent theclosed position, or vice versa. Based on the valve positions, SCREAM mayidentify the physical state of the process. As valve positions change,the process may enter a different state.

Once a model has been applied to process data to produce a predicteddescriptor characteristic of process state, a knowledge based system isconsulted to produce an output for process monitoring and/or controlpurposes. As shown in FIG. 3A, process manager 314 is communication withfirst and second knowledge based systems 170 a and 170 b.

Examples of such knowledge based systems include self-learning systems,expert systems, and logic systems, as well as so-called “fuzzy” variantsof each of these types of systems. An expert system is commonly definedas a computer system programmed to imitate problem-solving procedures ofa human expert. For example, in a medical system the user might enterdata like the patient's symptoms, lab reports, etc., and derive from thecomputer a possible diagnosis. The success of an expert system dependson the quality of the data provided to the computer, and the rules thecomputer has been programmed with for making deductions from that data.

An expert system may be utilized in conjunction with supervised learningfor purposes of process control. For example, where specific measureshave previously successfully been implemented to correct a processanomaly, these measures may serve as a training set and be utilized as abasis for addressing similar future problems.

While the above discussion has proposed analysis of process data throughapplication of a single model followed by consultation with a singleknowledge based system to obtain an output, the present invention is notlimited to this embodiment. For example, as shown in FIG. 3A processmanager 314 is in communication with first model 178 a and with a secondmodel 178 b. These models may be applied in parallel to obtain predicteddescriptors. These independently generated predicted descriptors can becross-referenced to validate the accuracy and reliability of processcontrol.

For example, where application of a first model produces a firstpredicted descriptor in agreement with a second predicted descriptor,the process state assessment is confirmed and the output may reflect adegree of certainty as to the state of the process. This reflection maybe in the form of the content of the output (i.e. a process fault isdefinitely indicated) and/or in the form of the output (i.e. a pager isactivated to immediately alert the human user to a high priority issue).

However, where first and second predicted descriptors resulting fromapplication of different models are not in agreement, a different outputmay be produced that reflects uncertainty in process state. Thisreflection may be in the form of the content of the output (i.e. aprocess fault may be indicated) and/or in the form of the output (i.e.only an email is sent to the human user to indicate a lower priorityissue.)

As an alternative approach, a second knowledge based system may beconsulted to resolve a conflict in predicted descriptors from differentmodels. An output based upon the descriptor chosen by the secondknowledge based system would then produced.

A wide variety, of structures may be utilized to detect processcharacteristics and/or modify operational process parameters. Data maybe received from a system in a variety of formats, such as text, stillimage, moving video images, and sound. FIG. 3B is a simplified diagramof a top-view 300 of an information capturing device according to anembodiment of the present invention. This diagram is merely an examplewhich should not limit the scope of the claims herein. One of ordinaryskill in the art would recognize many other variations, modifications,and alternatives.

As shown in FIG. 3B, the top view diagram includes an array of sensors,351A, 351B, 301C, 359 nth. The array is arranged in rows 351, 352, 355,357, 359 and columns, which are normal to each other. Each of thesensors has an exposed surface for capturing, for example, olfactoryinformation from fluids, e.g., liquid and/or vapor. The diagram shown ismerely an example of an information capturing device. Details of suchinformation capturing device are provided in U.S. application Ser. No.09/518,179, which is now U.S. Pat. No. 6,422,061, commonly assigned, andhereby incorporated by reference for all purposes. Other devices can bemade by companies such -as Aromascan (now Osmetech), Hewlett Packard,Alpha-MOS, or other companies.

Although the above has been described in terms of a capturing device forfluids including liquids and/or vapors, there are many other types ofcapturing devices. For example, other types of information capturingdevices for converting an intrinsic or extrinsic characteristic to ameasurable parameter can be used. These information capturing devicesinclude, among others, pH monitors, temperature measurement devices,humidity devices, pressure sensors, flow measurement devices, chemicaldetectors, velocity measurement devices, weighting scales, lengthmeasurement devices, color identification, and other devices. Thesedevices can provide an electrical output that corresponds to measurableparameters such as pH, temperature, humidity, pressure, flow, chemicaltypes, velocity, weight, height, length, and size.

In some embodiments, the present invention can be used with at least twosensor arrays. The first array of sensors comprises at least two sensors(e.g., three, four, hundreds, thousands, millions or even billions)capable of producing a first response in the presence of a chemicalstimulus. Suitable chemical stimuli capable of detection include, butare not limited to, a vapor, a gas, a liquid, a solid, an odor ormixtures thereof. This aspect of the device comprises an electronicnose. Suitable sensors comprising the first array of sensors include,but are not limited to conducting/nonconducting regions sensor, a SAWsensor, a quartz microbalance sensor, a conductive composite sensor, achemiresistor, a metal oxide gas sensor, an organic gas sensor, aMOSFET, a piezoelectric device, an infrared sensor, a sintered metaloxide sensor, a Pd-gate MOSFET, a metal FET structure, a electrochemicalcell, a conducting polymer sensor, a catalytic gas sensor, an organicsemiconducting gas sensor, a solid, electrolyte gas sensors, and apiezoelectric quartz crystal sensor. It will be apparent to those ofskill in the art that the electronic, nose array can be comprises ofcombinations of the foregoing sensors. A second sensor can be a singlesensor or an array of sensors capable of producing a second response inthe presence of physical stimuli. The physical detection sensors detectphysical stimuli. Suitable physical stimuli include, but are not limitedto, thermal stimuli, radiation stimuli, mechanical stimuli, pressure,visual, magnetic stimuli, and electrical stimuli.

Thermal sensors can detect stimuli which include, but are not limitedto, temperature, heat, heat flow, entropy, heat capacity, etc. Radiationsensors can detect stimuli that include, but are not limited to, gammarays, X-rays, ultra-violet rays, visible, infrared, microwaves and radiowaves. Mechanical sensors can detect stimuli which include, but are notlimited to, displacement, velocity, acceleration, force, torque,pressure, mass, flow, acoustic wavelength, and amplitude. Magneticsensors can detect stimuli that include, but are not limited to,magnetic field, flux, magnetic moment, magnetization, and magneticpermeability. Electrical sensors can detect stimuli which include, butare not limited to, charge, current, voltage, resistance, conductance,capacitance, inductance, dielectric permittivity, polarization andfrequency.

In certain embodiments, thermal sensors are suitable for use in thepresent invention that include, but are not limited to, thermocouples,such as a semiconducting thermocouples, noise thermometry,thermoswitches, thermistors, metal thermoresistors, semiconductingthermoresistors, thermodiodes, thermotransistors, calorimeters,thermometers, indicators, and fiber optics.

In other embodiments, various radiation sensors suitable for use in thepresent invention include, but are not limited to, nuclear radiationmicrosensors, such as scintillation counters and solid state detectors,ultra-violet, visible and near infrared radiation microsensors, such asphotoconductive cells, photodiodes, phototransistors, infrared radiationmicrosensors, such as photoconductive IR sensors and pyroelectricsensors.

In certain other embodiments, various mechanical sensors are suitablefor use in the present invention and include, but are not limited to,displacement microsensors, capacitive and inductive displacementsensors, optical displacement sensors, ultrasonic displacement sensors,pyroelectric, velocity and flow microsensors, transistor flowmicrosensors, acceleration microsensors, piezoresistivemicroaccelerometers, force, pressure and strain microsensors, andpiezoelectric crystal sensors.

In certain other embodiments, various chemical or biochemical sensorsare suitable for use in the present invention and include, but are notlimited to, metal oxide gas sensors, such as tin oxide gas sensors,organic gas sensors, chemocapacitors, chemodiodes, such as inorganicSchottky device, metal oxide field effect transistor (MOSFET),piezoelectric devices, ion selective FET for pH sensors, polymerichumidity sensors, electrochemical cell sensors, pellistors gas sensors,piezoelectric or surface acoustical wave sensors, infrared sensors,surface plasmon sensors, and fiber optical sensors.

Various other sensors suitable for use in the present invention include,but are not limited to, sintered metal oxide sensors, phthalocyaninesensors, membranes, Pd-gate MOSFET, electrochemical cells, conductingpolymer sensors, lipid coating sensors and metal FET structures. Incertain preferred embodiments, the sensors include, but are not limitedto, metal oxide sensors such as a Tuguchi gas sensors, catalytic gassensors, organic semiconducting gas sensors, solid electrolyte gassensors, piezoelectric quartz crystal sensors, fiber optic probes, amicro-electro-mechanical system device, a micro-opto-electro-mechanicalsystem device and Langmuir-Blodgett films.

Additionally, the above description in terms of specific hardware ismerely for illustration. It would be recognized that the functionalityof the hardware be combined or even separated with hardware elementsand/or software. The functionality can also be made in the form ofsoftware, which can be predominantly software or a combination ofhardware and software. One of ordinary skill in the art would recognizemany variations, alternatives, and modifications. Details of methodsaccording to the present invention are provided below.

A method of controlling a process according to one embodiment of thepresent invention may be briefly outlined as follows:

-   -   1. acquire initial data from a source at a first time;    -   2. convert the initial data into electronic form;    -   3. load the initial data into a first memory;    -   4. retrieve the initial data from the first memory;    -   5. acquire subsequent data from the source at a second time;    -   6. assign a first descriptor to the initial data and a second        descriptor to the subsequent data;    -   7. construct a model based on the initial data and the first        descriptor and on the subsequent data and the second descriptor;    -   8. store the model in a second memory;    -   9. acquire data from a process;    -   10. apply the model to the data to identify a predicted        descriptor characteristic of a state of the process; and    -   11. consult a knowledge based system and provide an output based        upon the predicted descriptor.

The above sequence of steps is merely an example of a way to monitor aprocess according to one embodiment of the present method and system.Details of these steps are provided below, but it is to be understoodthat one of ordinary skill in the art would recognize many othervariations, modifications, and alternatives.

The first step listed above is acquisition of initial data from a sourceat a first time. While data is to be acquired from at least one source,in many embodiments data will be acquired from a plurality of sources incontact with the process, for example the field mounted devicesillustrated and described in conjunction with FIG. 1A.

The second, third, and fourth listed steps are respectively, conversionof the initial data into electronic form, storage of the electronicdata, and retrieval of the stored data. Structures for performing thesesteps are well known in the art.

The fifth step is to acquire subsequent data from the source at a secondtime. This step provides the system with exemplary information aboutchanges in the process between the first time and the second time. Whilein its most general form the present invention samples data from twotime periods, in practice it is expected that data from many times willbe acquired.

The sixth step is to assign a first descriptor to the initial data and asecond descriptor to the subsequent data. The descriptor characterizesthe state of the process in relation to the data. Examples of possibledescriptors include “normal process operation,” “process start-up,”“process shut-down,” “over heat condition,” etc.

The seventh step is to construct a model of process behavior based uponthe initial and subsequent data and the first and second descriptors.While at least one model is constructed, in practical implementation ofthe present invention many types of models based upon differentprinciples may be constructed utilizing approaches such as univariatestatistical techniques, time series analysis, and multivariatestatistical techniques such as PCA, CDA, and PLS, as are known to one ofordinary skill in the art.

Once the model has been constructed, the eighth step is to store themodel in a second memory. In the ninth step, the stored model is appliedto a set of data acquired from the process. This data set can mayrepresent real time parameters of the process that is to be monitoredand/or controlled.

In the tenth step, the model is applied to the third data set to producea predicted descriptor that characterizes the state of the process. Thispredicted descriptor is output by the model based upon the constructionof the model, utilizing the initial data, the subsequent data, the firstdescriptor, and the second descriptor.

Based upon the predicted descriptor predicted by application of themodel, in the eleventh and final step a knowledge based system isreferenced and an output is provided. This output may be provided to aninternal entity such as a process control device, or to an externalentity such as associated s supply chain management system (SCM), or toboth internal and external systems. For example, where the thirddescriptor predicted by the model indicates failure of a pump, an outputin the form of a purchase order with the relevant replacement pump partnumber could be communicated to the SCM. Alternatively or in conjunctionwith notifying an SCM system, the output could be directed to an entitysuch as a pager or voicemail, thereby communicating the state of theprocess to a human operator for monitoring and/or possible intervention.

The above listed steps represent only a specific example of a method formonitoring and controlling a process in accordance with an embodiment ofthe present invention. One of ordinary skill in the art would recognizemany variations, alternatives, and modifications.

For example, many models useful for predicting process behavior may becreated utilizing univariate and multivariate statistical techniquesapplied to previously collected data. Alternatively however, usefulmodels of process behavior may also be constructed from mathematicalexpressions of physical or natural laws. Where such a physical model isemployed, rules implicit in the model may govern predicted behavior ofthe system over time. Prior collection of data may therefore not benecessary to create the model, and the model may be directly applied todata acquired from the process.

In yet another possible embodiment, data from the process may be-analyzed in parallel by more than one model. In embodiments of thepresent invention where multiple models are being used to predictprocess behavior, the descriptor output by each model may be compared. Adifference in the descriptor predicted by the various models could beresolved through application of a knowledge based system such as anexpert system.

A method using digital information for populating a database foridentification or classification purposes according to the presentinvention may be briefly outlined as follows:

-   -   1. Acquire data, where the data are for one or more substances,        each of the substances having a plurality of distinct        characteristics;    -   2. Convert data into electronic form;    -   3. Provide data in electronic form (e.g., text, normalized data        from an array of sensors) for classification or identification;    -   4. Load the data into a first memory by a computing device;    -   5. Retrieve the data from the first memory;    -   6. Remove first noise levels from the data using one or more        filters;    -   7. Correct data to a base line for one or more variables such as        drift, temperature, humidity, etc.;    -   8. Normalize data using, a base line;    -   9. Reject one or more of the plurality of distinct        characteristics from the data;    -   10. Perform one or more pattern recognition methods on the data;    -   11. Classify the one or more substances based upon the pattern        recognition methods to form multiple classes that each        corresponds to a different substance;    -   12. Determine optimized (or best general fit) pattern        recognition method via cross validation process;    -   13 Store the classified substances into a second memory for        further analysis; and    -   14. Perform other steps, as desirable.

The above sequence of steps is merely an example of a way to teach ortrain the present method and system. The present example takes more thanone different substance, where each substance has a plurality ofcharacteristics, which are capable of being detected by sensors. Each ofthese characteristics are measured, and then fed into the present methodto create a training set. The method includes a variety of dataprocessing techniques to provide the training set. Depending upon theembodiment, some of the steps may be separated even further or combined.Details of these steps are provided below according to Figs.

FIGS. 4A to 4C are simplified diagrams of methods 400 according toembodiments of the present-invention. These diagrams are merely exampleswhich should not limit the scope of the claims herein. One of ordinaryskill in the art would recognize many other variations, modifications,and alternatives. As shown, the present method begins at start, step401. The method then captures data (step 403) from a data acquisitiondevice. The data acquisition device can be any suitable device forcapturing either intrinsic or extrinsic information from a substance. Asmerely an example, the present method uses a data acquisition device forcapturing olfactory information. The device has a plurality of sensors,which convert a scent or olfaction print into an artificial orelectronic print. In a specific embodiment, such data acquisition deviceis disclosed in WO 99/47905, commonly assigned and hereby incorporatedby reference for all purposes. Those of skill in the art will know ofother devices including other electronic noses suitable for use in thepresent invention. In a specific embodiment, the present inventioncaptures olfactory information from a plurality of different liquids,e.g., isopropyl alcohol, water, toluene. The olfactory information fromeach of the different liquids is characterized by a plurality ofmeasurable characteristics, which are acquired by the acquisitiondevice. Each different liquid including the plurality of measurablecharacteristics can be converted into an electronic data form for useaccording to the present invention. Some of these characteristics werepreviously described, but can also include others.

Next, the method transfers the electronic data, now in electronic form,to a computer aided process (step 405). The computer aided process maybe automatic and/or semiautomatic depending upon the application. Thecomputer aided process can store the data into memory, which is coupledto a processor. When the data is ready for use, the data is loaded intothe process, step 407. In embodiments where the data has been stored,they are retrieved and then loaded into the process. Preferably, thedata can be loaded onto workspace to a text file or loaded into a spreadsheet for analysis. Here, the data can be loaded continuously andautomatically, or be loaded manually, or be loaded and monitoredcontinuously to provide real time analysis.

The method filters the data (step 411) to remove any imperfections. Asmerely an example, data from the present data acquisition device areoften accompanied with glitches, high frequency noise, and the like.Here, the signal to noise ratio is often an important consideration forpattern recognition especially when concentrations of analytes are low,exceedingly high, or not within a predefined range of windows accordingto some embodiments. In such cases, it is desirable to boost the signalto noise ratio using the present digital filtering technology. Examplesof such filtering technology includes, but is not limited to a ZeroPhase-Filter, an Adaptive Exponential Moving Average Filter, and aSavitzky-Golay Filter, which will be described in more detail below.

Optionally, the filtered responses can be displayed, step 415. Here, thepresent method performs more than one of the filtering techniques todetermine which one provides better results. By way of the presentmethod, it is possible to view the detail of data preprocessing. Themethod displays outputs (step 415) for each of the sensors, where signalto noise levels can be visually examined. Alternatively, analyticaltechniques can be used to determine which of the filters worked best.Each of the filters are used on the data, step 416 via branch 418. Oncethe desired filter has been selected, the present method goes to thenext step.

The method performs a baseline correction step (step 417). Dependingupon the embodiment, there can be many different ways to implement abaseline correction method. Here, the baseline correction method findsresponse peaks, calculates ΔR/R, and plots the ΔR/R verses time stamps,where the data have been captured. It also calculates maximum ΔR/R andmaximum slope of ΔR/R for further processing. Baseline drift is oftencorrected by way of the present step. Once baseline drift has beencorrected, the present method undergoes a normalization process,although other processes can also be used. Here, ΔR/R can be determinedusing one of a plurality of methods, which are known, if any, ordeveloped according to the present invention.

As merely an example, FIG. 4C illustrates a simplified plot of a signaland various components used in the calculation of ΔR/R, which can beused depending upon the embodiment. This diagram is merely anillustration, which should not limit the scope of the claims herein. Oneof ordinary skill in the art would recognize many other variations,modifications, and alternatives. As shown, the diagram shows a pulse,which is plotted along a time axis, which intersects a voltage, forexample. The diagram includes, a ΔR (i.e., delta R), which is definedbetween R and R(max). As merely an example, ΔR/R is defined by thefollowing expression:ΔR/R═(R(max)−R(0))/R

-   -   where    -   ΔR is defined by the average difference between a base line        value R(0) and    -   R(max);    -   R(max) is defined by a maximum value of R;    -   R(0) is defined by an initial value of R; and    -   R is defined as a variable or electrical measurement of        resistance from a sensor, for example.

This expression is merely an example, the term ΔR/R could be defined bya variety of other relationships. Here, ΔR/R has been selected in amanner to provide an improved signal to noise ratio for the signals fromthe sensor, for example. There can be many other relationships thatdefine ΔR/R, which may be a relative relation in another manner.Alternatively, ΔR/R could be an absolute relationship or a combinationof a relative relationship and an absolute relationship. Of course, oneof ordinary skill in the art would provide many other variations,alternatives, and modifications.

As noted, the method includes a normalization step, step 419. In someembodiments, normalization is a row wise operation. Here, the methoduses a so-called area normalization. After such normalization method,the sum of data along each row is unity. Vector length normalization isalso used, where the sum of data squared of each row equals unity.

As shown by step 421, the method may next perform certain preprocessingtechniques. Preprocessing may be employed to eliminate the effect on thedata of inclusion of the mean value in data analysis, or of the use ofparticular units of measurement, or of large differences in the scale ofthe different data types received. Examples of such preprocessingtechniques include mean-centering and auto-scaling. Preprocessingtechniques utilized for other purposes include for example, smoothing,outlier rejection, drift monitoring, and others. Some of thesetechniques will be described later. Once preprocessing has beencompleted, the method performs a detailed processing technique.

Next, the method performs a main process for classifying each of thesubstances according to each of their characteristics, step 423. Here,the present method performs a pattern recognition process, such as theone illustrated by the simplified diagram 430 in FIG. 4B. This diagramis merely an example, which should not limit the scope of the claimsherein. One of ordinary skill in the art would recognize many othervariations, modifications, and alternatives.

As shown, the method 430 begins with start, step 428. The method queriesa library, including a plurality of pattern recognition algorithms, andloads (step 431) one or more of the algorithms in memory to be used. Themethod selects the one algorithm, step 432, and runs the data throughthe algorithm, step 433. In a specific embodiment, the patternrecognition process uses more than one algorithms, which are known, arepresently being developed, or will be developed in the future. Theprocess is used to find weighting factors based upon descriptors foreach of the characteristics to ultimately determine an identifiablepattern to describe the activity of a process. The present method runsthe data, which have been preprocessed, through each of the algorithms.

PCA Principal Components Analysis

HCA Hierarchical Cluster Analysis

KNN CV K Nearest Neighbor Cross Validation

KNN Prd K Nearest Neighbor Prediction

SLMCA CV SIMCA Cross Validation

SIMCA Prd SIMCA Prediction

Canon CV Canonical Discriminant Analysis and Cross Validation

Canon Prd Canonical Discriminant Prediction

Fisher CV Fisher Linear Discriminant Analysis and Cross Validation

Fisher Prd Fisher Linear Discriminant Prediction

SCREAM System Coherence Rendering Exception Analysis for Maintenance

PCA and HCA, are unsupervised learning methods. They can be used forinvestigating training data and finding the answers of:

-   -   I. How many principal components will cover the most of        variances?    -   II. How many principal components you have to choose?    -   III. How do the loading plots look?    -   IV. How do the score plots look?    -   V. How are the scores separated among the classes?    -   VI. How are the clusters grouped in their classes?    -   VII. How much are the distances among the clusters?        The other four algorithms, KNN CV, SIMCA CV, Canon CV, and        Fisher CV, are supervised learning methods used when the goal is        to construct models to be used to predict the future behavior of        a process. These algorithms will perform cross validation, find        the optimum number of parameters, and build models. SCREAM is        actually a combination of several techniques employing time        series analysis.

Once the data has been run through the first algorithm, for example, themethod repeats through a branch (step 435) to step 432 to anotherprocess. This process is repeated until one or more of the algorithmshave been used to analyze the data. The process is repeated to try tofind a desirable algorithm that provides good results with a specificpreprocessing technique used to prepare the data. If all of thedesirable algorithms have been used, the method stores (or haspreviously stored) (step 437) each of the results of the processes onthe data in memory.

In a specific embodiment, the present invention provides across-validation technique. Here, an auto (or automatic)cross-validation algorithm can be implemented. The present techniqueuses cross-validation, which is an operation process used to validatemodels built with chemometrics algorithms based on training data set.During the process, the training data set is divided into calibrationand validation subsets. A model is built with the calibration subset andis used to predict the validation subset. The training data set can bedivided into calibration and validation subsets called “leave-one-out,”i.e., take one sample out from each class to build a validation subsetand use the rest samples to build a calibration subset. This process canbe repeated using different subset until every sample in the trainingset has been included in one validation subset. The predicted resultsare stored in an array. Then, the correct prediction percentages (CPP)are calculated, and are used to validate the performance of the model.

According to the present method, a cross-validation with one trainingdata set can be applied to generally all the models built with differentalgorithms, such as K-Nearest Neighbor (KNN), SIMCA, CanonicalDiscriminant Analysis, Fisher Linear Discriminant Analysis, and SCREAMrespectively. The results of correct prediction percentages (CPP) showthe performance differences with the same training data set but withdifferent algorithms. Therefore, one can pickup the best algorithmaccording to the embodiment.

During the model building, there are several parameters and options tochoice. To build the best model with one algorithm, cross-validation isalso used to find the optimum parameters and options. For example, inthe process of building a KNN model, cross-validation is used tovalidate the models built with different number of K, different scalingoptions, e.g., mean-centering or auto-scaling, and other options, e.g.,with PCA or without PCA, to find out the optimum combination of K andother options. In a preferred embodiment, auto-cross-validation can beimplemented using a single push-button or two push buttons for ease inuse. It will automatically run the processes mentioned above over allthe (or any selected) algorithms with the training data set to find outthe optimum combination of parameters, scaling options and algorithms.

The method also performs additional steps of retrieving data, step 438,and retrieving the process or algorithm, step 439. As noted, each of theprocesses can form a descriptor for each sample in the training set.Each of these descriptors can be stored and retrieved. Here, the methodstores the raw data, the preprocessed data, the descriptors, and thealgorithm used for the method for each algorithm used according to thepresent invention. The method stops, step 441.

The above sequence of steps is merely illustrative. The steps can beperformed using computer software or hardware or a combination ofhardware and software. Any of the above steps can also be separated orbe combined, depending upon the embodiment. In some cases, the steps canalso be changed in order without limiting the scope of the inventionclaimed herein. One of ordinary skill in the art would recognize manyother variations, modifications, and alternatives.

An alternative method according to the present invention is brieflyoutlined as follows:

-   -   1. Acquire raw data in voltages;    -   2. Check base line voltages;    -   3. Filter;    -   4. Calculate ΔR/R    -   5. Determine Training set?    -   6. If yes, find samples (may repeat process);    -   7. Determine outlier?;    -   8. If yes, remove bad data using, for example PCA;    -   9. Find important sensors using importance index (individual        filtering process);    -   10. Normalize;    -   11. Find appropriate pattering recognition process;    -   12. Run each pattern recognition process;    -   13. Display (optional);    -   14. Find best fit out of each pattern recognition process;    -   15. Compare against confidence factor (if less than a certain        number, this does not work);    -   16. Perform other steps, as required.

The above sequence of steps is merely an example of a way to teach ortrain the present method and system according to an alternativeembodiment. The present example takes more than one different substance,where each substance has a plurality of characteristics, which arecapable of being detected by sensors or other sensing devices. Each ofthese characteristics are measured, and then fed into the present methodto create a training set. The method includes a variety of dataprocessing techniques to provide the training set. Depending upon theembodiment, some of the steps may be separated even further or combined.Details of these steps are provided below according to Figs.

FIGS. 4D and 4E are simplified of methods 450 according to embodimentsof the present invention. These diagrams are merely examples whichshould not limit the scope of the claims herein. One of ordinary skillin the art would recognize many other variations, modifications, andalternatives. As shown, the present method begins at step 451. Here, themethod begins at a personal computer host interface, where the methodprovides a training set of samples (which are each defined as adifferent class of material) to be analyzed or an unknown sample (oncethe training set has been processed). The training set can be derivedfrom a plurality of different samples of fluids (or other substances orinformation). The samples can range in number from more than one to morethan five or more than ten or more than twenty in some applications. Thepresent method processes one sample at a time through the method thatloops back to step 451 via the branch indicated by reference letter B,for example, from step 461, which will be described in more detailbelow.

In a specific embodiment, the method has captured data about theplurality of samples from a data acquisition device. Here, each of thesamples should form a distinct class of data according to the presentinvention. The data acquisition device can be any suitable device forcapturing either intrinsic or extrinsic information from a substance. Asmerely an example, the present method uses a data acquisition device forcapturing olfactory information. The device has a plurality of sensorsor sensing devices, which convert a scent or olfaction print into anartificial or electronic print. In a specific embodiment, such dataacquisition device is disclosed in WO 99/47905, commonly assigned andhereby incorporated by reference for all purposes. Those of skill in theart will know of other devices including other electronic noses suitablefor use in the present invention. In a specific embodiment, the presentinvention captures olfactory information from a plurality of differentliquids, e.g., isopropyl alcohol, water, toluene. The olfactoryinformation from each of the different liquids is characterized by aplurality of measurable characteristics, which are acquired by theacquisition device. Each different liquid including the plurality ofmeasurable characteristics can be converted into an electronic data formfor use according to the present invention.

The method acquires the raw data from the sample in the training setoften as a voltage measurement, step 452. The voltage measurement isoften plotted as a function of time. In other embodiments, there aremany other ways to provide the raw data. For example, the raw data canbe supplied as a resistance, a capacitance, an inductance, a binarycharacteristic, a quantized characteristic, a range value or values, andthe like. Of course, the type of raw data used depends highly upon theapplication. In some embodiments, the raw data can be measured multipletimes, where an average is calculated. The average can be a timeweighted value, a mathematical weighted value, and others.

Next, the method checks the base line voltages from the plurality ofsensing devices used to capture information from the sample, as shown instep 453. The method can perform any of the base line correction methodsdescribed herein, as well as others. Additionally, the method can merelycheck to see if each of the sensing devices has an output voltage withina predetermined range. If each of the sensing devices has an outputvoltage within a predetermined range, each of the sensing devices has abase line voltage that is not out of range. Here, the method continuesto the next step. Alternatively, the method goes to step 455, whichrejects the sensing device that is outside of the predetermined voltagerange, and then continues to the next step. In some embodiments, thesensing device that is outside of the range is a faulty or bad sensor,which should not be used for training or analysis purposes.

The method then determines if the measured voltage for each sensingdevice is within a predetermined range, step 454. The voltage for eachsensor is provided by exposing the sensor to the sample. The exposurecan be made for a predetermined amount of time. Additionally, theexposure can be repeated and averaged, either by time or geometrically.The voltage is compared with a range or set of ranges, which oftencharacterize the sensor for the exposure. If the exposed sensing deviceis outside of its predetermined range for the exposure, the method canreject (step 455) the sensor and proceed to the next step. The rejectedsensor may be faulty or bad. Alternatively, if each of the sensingdevices in, for example, in the array of sensors is within a respectivepredetermined range, then the method continues to the next step, whichwill be discussed below.

The method can convert the voltage into a resistance value, step 456.Alternatively, the voltage can be converted to a capacitance, aninductance, an impedance, or other measurable characteristic. In someembodiments, the voltage is merely converted using a predeterminedrelationship for each of the sensing devices. Alternatively, there maybe a look up table, which correlates voltages with resistances. Stillfurther, there can be a mathematical relationship that correlates thevoltage with the resistance.

The method the runs the data through one or more filters, step 457. Themethod filters the data to remove any imperfections, noise, etc. Asmerely an example, data from the present data acquisition device areoften accompanied with glitches, high frequency noise, and the like.Here, the signal to noise ratio is often an important consideration forpattern recognition especially when concentrations of analytes are low,exceedingly high, or not within a predefined range of windows accordingto some embodiments. In such cases, it is desirable to boost the signalto noise ratio using the present digital filtering technology. Examplesof such filtering technology includes, but is not limited to a ZeroPhase Filter, an Adaptive Exponential Moving Average Filter, and aSavitzky-Golay Filter, which will be described in more detail below.

The method runs a response on the data, step 458. Here, the method mayperform a baseline correction step. Depending upon the embodiment, therecan be many different ways to implement a baseline correction method.Here, the baseline correction method finds response peaks, calculatesΔR/R, and plots the ΔR/R verses time stamps, where the data have beencaptured. It also calculates maximum ΔR/R and maximum slope of ΔR/R forfurther processing. Baseline drift is often corrected by way of thepresent step. Once baseline drift has been corrected, the present methodundergoes a normalization process, although other processes can also beused. Here, ΔR/R can be determined using one of a plurality of methods,which are known, if any, or developed according to the presentinvention.

In the present embodiment, the method is for analyzing a training set ofsubstances, step 459 (in FIG. 4E). The method then continues to step461. Alternatively, the method skips to step 467, which will bedescribed in one or more of the copending applications. If there isanother substances in the training set to be analyzed (step 459), themethod returns to step 452 via branch B, as noted above. Here, themethod continues until each of the substances in the training set hasbeen run through the process in the present preprocessing steps. Theother samples will run through generally each of the above steps, aswell as others, in some embodiments.

Next, the method goes to step 463. This step determines if any of thedata has an outlier. In the present embodiment, the outlier is a datapoint, which does not provide any meaningful information to the method.Here, the outlier can be a data point which is outside of the noiselevel, where no conclusions can be made. The outlier is often thought ofa data point that is tossed out due to statistical deviations. That is,lowest and highest data points can be considered as outliers in someembodiments. If outliers are found, step 463, the method can retake(step 465) samples, which are exposed to the sensing devices, that havethe outliers. The samples that are retaken loop back through the processvia the branch indicated by reference letter B. Outliers can be removedfrom the data in some embodiments.

The method also can uncover important sensors using an importance index(individual filtering process). Here, the method identifies whichsensors do not provide any significant information by comparing a likesensor output with a like sensor output for each of the samples in thetraining set. If certain sensors are determined to have little influencein the results, these sensors are ignored (step 473) and then continuesto the next step, as shown in the Fig. Alternatively, if generally allsensors are determined to have some significance, the method continuesto step 467.

Next, the method performs post processing procedures (step 467), asdefined herein. The post processing procedures include, for example, anormalization step. In a specific embodiment, the normalization stepscales the data to one or other reference value and then autoscales thedata so that each sample value is referenced against each other. If thedata is for the training step, step 468, the method continues to apattern recognition cross-validation process, step 469, the crossvalidation process is used with step 470.

The pattern recognition process uses more than one algorithms, which areknown, are presently being developed, or will be developed in thefuture. The process is used to find weighting factors for each of thecharacteristics to ultimately determine an identifiable pattern touniquely identify each of the substances. The present method runs thedata, which have been preprocessed, through each of the algorithms.

-   -   PCA Principal Components Analysis    -   HCA Hierarchical Cluster Analysis    -   KNN CV K Nearest Neighbor Cross Validation    -   KNN Prd K Nearest Neighbor Prediction    -   SIMCA CV SIMCA Cross Validation    -   SIMCA Prd SIMCA Prediction    -   Canon CV Canonical Discriminant Analysis and Cross Validation    -   Canon Prd Canonical Discriminant Prediction    -   Fisher CV Fisher Linear Discriminant Analysis and Cross        Validation    -   Fisher Prd Fisher Linear Discriminant Prediction    -   SCREAM System Coherence Rendering Exception Analysis for        Maintenance        PCA and HCA, are unsupervised learning methods. They are used        for investigating training data and finding the answers of:    -   I. How many principal components will cover the most of        variances?    -   II. How many principal components you have to choose?    -   III. How do -the loading plots look?    -   IV. How do the score plots look?    -   V. How are the scores separated among the classes?    -   VI. How are the clusters grouped in their classes?    -   VII. How much are the-distances among the clusters?        The other four algorithms, KNN CV, SIMCA CV, Canon CV, and        Fisher CV, are supervised learning methods used when the goal is        to construct models to be used to predict the future behavior of        a process. These algorithms will do cross validation, find the        optimum number of parameters, and build models. SCREAM is a        combination of several techniques employing time series        analysis.

In a specific embodiment, the present invention provides across-validation technique. Here, an auto (or automatic)cross-validation algorithm can be implemented. The present techniqueuses cross-validation, which is an operation process used to validatemodels built with chemometrics algorithms based on training data set.During the process, the training data set is divided into calibrationand validation subsets. A model is built with the calibration subset andis used to predict the validation subset. The training data set can bedivided into calibration and validation subsets called “leave-one-out,”i.e., take one sample out from each class to build a validation subsetand use the rest samples to build a calibration subset. This process canbe repeated using different subset until every sample in the trainingset has been included in one validation subset. The predicted resultsare stored in an array. Then, the correct prediction percentages (CPP)are calculated, and are used to validate the performance of the model.

According to the present method, a cross-validation with one trainingdata set can be applied to generally all the models built with differentalgorithms, such as K-Nearest Neighbor (KNN), SIMCA, CanonicalDiscriminant Analysis, and Fisher Linear Discriminant Analysis,respectively. The results of correct prediction percentages (CPP) showthe performance differences with the same training data set but withdifferent algorithms. Therefore, one can pick up the best algorithmaccording to the embodiment, as shown in step 470.

During model building, several parameters and options may be chosen. Tobuild the best model with one algorithm, cross-validation is also usedto find the optimum parameters and options. For example, in the processof building a KNN model, cross-validation is used to validate the modelsbuilt with different number of K, different scaling options, e.g.,mean-centering or auto-scaling, and other options, e.g., with PCA orwithout PCA, to find out the optimum combination of K and other options.In a preferred embodiment, auto-cross-validation can be implementedusing a single push-button or two push buttons for ease in use. It willautomatically run the processes mentioned above over all the (or anyselected) algorithms with the training data set to find out the optimumcombination of parameters, scaling options and algorithms.

Once the best fit algorithm and model has been uncovered, the methodgoes through a discrimination test, step 471. In a specific embodiment,the method compares the results, e.g., fit of data against algorithm,combination of data and other preprocessing information, againstconfidence factor (if less than a certain number, this does not work).This step provides a final screen on the data, the algorithm used, thepreprocessing methods, and other factors to see if everything just makessense. If so, the method selects the final combination of techniquesused according to an embodiment of the present invention.

The above sequence of steps is merely illustrative. The steps can beperformed using computer software or hardware or a combination ofhardware and software. Any of the above steps can also be separated orbe combined, depending upon the embodiment. In some cases, the steps canalso be changed in order without limiting the scope of the inventionclaimed herein. One of ordinary skill in the art would recognize manyother variations, modifications, and alternatives. An example accordingto the present invention is described in U.S. Ser. No. 09/802,513, whichis incorporated by reference for all purposes.

The above example is merely an illustration, which should not undulylimit the scope of the claims herein. One of ordinary skill in the artwould recognize many other variations, modifications, and alternatives.

It is also understood that the examples and embodiments described hereinare for illustrative purposes only and that various modifications orchanges in light thereof will be suggested to persons skilled in the artand are to be included within the spirit and purview of this applicationand scope of the appended claims. All publications, patents, and patentapplications cited herein are hereby incorporated by reference for allpurposes in their entirety.

An alternative method for identification or classification purposesaccording to the present invention is briefly outlined as follows:

-   -   1. Provide unknown sample;    -   2. Acquire raw data in voltages;    -   3. Check base line voltages;    -   4. Filter;    -   5. Calculate ΔR/R    -   6. Determine Training set?    -   7. If yes, use method outlined above;    -   8. Otherwise, normalize;    -   9. If training set, use method outlined above;    -   10. Otherwise, find appropriate pattern recognition process from        method above for training set;    -   11. Output result from pattern recognition process;    -   12. Check confidence level;    -   13. If greater than predetermined amount, go to next step,        otherwise, report the name and probability of closest class;    -   14. Make prediction and report probability; and    -   15. Perform other steps, as required.

The above sequence of steps is merely an example of a way to identify orclassify an unknown sample or known sample of unknown quality accordingto an alternative embodiment. The present example takes one substance orsample, where the substance has a plurality of characteristics, whichare capable of being detected by sensors or other sensing devices. Eachof these characteristics is measured, and then fed into the presentmethod to create a training set. The method includes a variety of dataprocessing techniques to provide the training set. Depending upon theembodiment, some of the steps may be separated even further or combined.Details of these steps are provided below according to Fig.

As shown, the present method (450) begins at step 451. Here, the methodbegins at a personal computer host interface, where the method providesa sample to be analyzed or an unknown sample (once the training set hasbeen processed). The present method processes a known sample of unknownquality to determine if the quality is within or outside of apredetermined range. Alternatively, the sample may be unknown and thesample classification is determined according to an embodiment of thepresent invention. In a specific embodiment, the method has captureddata about the sample from a data acquisition device. Here, the sampleshould form a distinct class of data according to the present invention.The data acquisition device can be any suitable device for capturingeither intrinsic or extrinsic information from a substance. As merely anexample, the present method uses a data acquisition device for capturingolfactory information. The device has a plurality of sensors or sensingdevices, which convert a scent or olfaction print into an artificial orelectronic print. In a specific embodiment, such data acquisition deviceis disclosed in WO 99/47905, commonly assigned and hereby incorporatedby reference for all purposes. Those of skill in the art will know ofother devices including other electronic noses suitable for use in thepresent invention. In a specific embodiment, the present inventioncaptures olfactory information from a plurality of different liquids,e.g., isopropyl alcohol, water, toluene. The olfactory information fromeach of the different liquids is characterized by a plurality ofmeasurable characteristics, which are acquired by the acquisitiondevice. Each different liquid including the plurality of measurablecharacteristics can be converted into an electronic data form for useaccording to the present invention.

The method acquires the raw data from the sample often as a voltagemeasurement, step 452. The voltage measurement is often plotted as afunction of time. In other embodiments, there are many other ways toprovide the raw data. For example, the raw data can be supplied as aresistance, a capacitance, an inductance, a binary characteristic, aquantified characteristic, a range value or values, and the like. Ofcourse, the type of raw data used depends highly upon the application.In some embodiments, the raw data can be measured multiple times, wherean average is calculated. The average can be a time weighted value, amathematical weighted value, and others.

Next, the method checks the base line voltages from the plurality ofsensing devices used to capture information from the sample, as shown instep 453. The method can perform any of the base line correction methodsdescribed herein, as well as others. Additionally, the method can merelycheck to see if each of the sensing devices has an output voltage withina predetermined range. If each of the sensing devices has an outputvoltage within a predetermined range, each of the sensing devices has abase line voltage that is not out of range. Here, the method continuesto the next step. Alternatively, the method goes to step 455, whichrejects the sensing device that is outside of the predetermined voltagerange, and then continues to the next step. In some embodiments, thesensing device that is outside of the range is a faulty or bad sensor,which should not be used for training or analysis purposes.

The method then determines if the measured voltage for each sensingdevice is within a predetermined range, step 454. The voltage for eachsensor is provided by exposing the sensor to the sample. The exposurecan be made for a predetermined amount of time. Additionally, theexposure can be repeated and averaged, either by time or geometrically.The voltage is compared with a range or set of ranges, which oftencharacterize the sensor for the exposure. If the exposed sensing deviceis outside of its predetermined range for the exposure, the method canreject (step 455) the sensor and proceed to the next step. The rejectedsensor may be faulty or bad. Alternatively, if each of the sensingdevices in, for example, in the array of sensors is within a respectivepredetermined range, then the method continues to the next step, whichwill be discussed below.

The method can convert the voltage into a resistance value, step 456.Alternatively, the voltage can be converted to a capacitance, aninductance, an impedance, or other measurable characteristic. In someembodiments, the voltage is merely converted using a predeterminedrelationship for each of the sensing devices. Alternatively, there maybe a look up table, which correlates voltages with resistances. Stillfurther, there can be a mathematical relationship that correlates thevoltage with the resistance.

The method the runs the data through one or more filters, step 457. Themethod filters the data to remove any imperfections, noise, etc. Asmerely an example, data from the present data acquisition device areoften accompanied with glitches, high frequency noise, and the like.Here, the signal to noise ratio is often an important consideration forpattern recognition especially when concentrations of analytes are low,exceedingly high, or not within a predefined range of windows accordingto some embodiments. In such cases, it is desirable to boost the signalto noise ratio using the present digital filtering technology. Examplesof such filtering technology includes, but is not limited to a ZeroPhase Filter, an Adaptive Exponential Moving Average Filter, and aSavitzky-Golay Filter, which will be described in more detail below.

The method runs a response on the data, step 458. Here, the method mayperform a baseline correction step. Depending upon the embodiment, therecan be many different ways to implement a baseline correction method.Here, the baseline correction method finds response peaks, calculatesΔR/R, and plots the ΔR/R verses time stamps, where the data have beencaptured. It also calculates maximum ΔR/R and maximum slope of ΔR/R forfurther processing. Baseline drift is often corrected by way of thepresent step. Once baseline drift has been corrected, the present methodundergoes a normalization process, although other processes can also beused. Here, ΔR/R can be determined using one of a plurality of methods,which are known, if any, or developed according to the presentinvention.

In a specific embodiment, most of the preprocessing steps, as notedabove, were determined by optimum combinations of processes from thetraining set. The sample is run through the same or similar set ofpreprocessing steps. In the present embodiment, the method skips to step467. The post processing procedures include, for example, anormalization step. In a specific embodiment, the normalization stepscales the data to one or other reference value and then autoscales thedata so that the sample value is referenced against each other (step467).

Since the sample is not part of the training set process (step 468), themethod goes to step 475. Here, the unknown sample is run through thealgorithm selected from the training procedure, step 475. The trainingset uncovered the optimum or near optimum algorithm to be used by theunknown sample, which should fall into one of the classes from thetraining set. The sample is run through calculations (step 476) and aresult or results are outputted. The result is outputted through aconfidence factor (step 477). If the result is greater than apredetermined amount, the method goes to step 479. Alternatively, themethod outputs a result (step 478), where the name and probability ofthe closest (step 455).

In step 479, the method makes the prediction and reports theprobability. In some embodiments, the method identifies the unknownsample based upon its descriptor that matches a known class of samplesfrom the training set. Alternatively, the method identifies that thesample, which is known, but may be of unknown quality, is within apredetermined range of values. Here, the method can determine if asample, which has been derived from an industrial process, for example,is within a predetermined specification from a training step. The samplecan be a final product, an intermediary product, or any other stage ofmanufacture or processing.

The above sequence of steps is merely illustrative. The steps can beperformed using computer software or hardware or a combination ofhardware and software. Any of the above steps can also be separated orbe combined, depending upon the embodiment. In some cases, the steps canalso be changed in order without limiting the scope of the inventionclaimed herein. One of ordinary skill in the art would recognize manyother variations, modifications, and alternatives. The above example ismerely an illustration, which should not unduly limit the scope of theclaims herein. One of ordinary skill in the art would recognize manyother variations, modifications, and alternatives.

For example, while the above description focuses upon use of embodimentsof the present invention to control an industrial process, the presentinvention is not limited to this application. The present invention isgenerally applicable to monitoring the state of complex processes, andcan be utilized, for instance, to monitor the ongoing health of a pieceof capital equipment such as pump, compressor, or paper manufacturingmachine.

Moreover, the present invention is not limited to monitoring industrialprocesses. Other complex processes may be monitored in accordance withembodiments of the present invention. For example, an embodiment of thepresent invention could be utilized for human medical diagnosis, withnon-symbolic inputs such as heart rate, medical history, blood testsetc. being combined with symbolic information such as patient demeanor,skin texture and color, etc. Based upon the various inputs, a systemcould provide a threshold patient assessment, and even suggest changesin treatment, subject, of course to supervision and intervention by atrained physician.

EXAMPLES

To prove the operation of the present invention, we made a softwarespecification document, which can be used to implement aspects of theinvention. This specification is merely an example and should not undulylimit the scope of the claims herein. One of ordinary skill in the artwould recognize many other variations, modifications, and alternatives.For easy reading, we have provided an outline of the Table of Contentsfor the specification as follows:

-   -   SYSTEM REQUIREMENTS    -   PROJECT DESCRIPTION    -   PRODUCT DEFINITION    -   FUNCTIONAL SPECIFICATIONS    -   OPERATIONS ENVIRONMENT    -   APPENDICES    -   GLOSSARY    -   SYSTEM REQUIREMENTS

We have prepared the information below to define computer software,including a software product for process control. The software has beenmade to analyze sensor data from diverse data sources in a plant orother manufacturing environment. A software product able to provideadvanced analysis capabilities would fill an unmet need and offer valuein a number of market sectors. By using advanced analytical techniques,better prediction is possible that, in turn, provides improved productquality, increased reliability, less downtime, and other benefits.Various tests have been conducted with key partners in select verticalmarkets. Analysis of data from a petrochemical pilot plant, andexperiments involving smoke and fire detection both yielded positiveresults, and has encouraged the work to develop a robust softwareproduct to proceed.

In the present example, we will develop a modular set ofweb/browser-based software products that allows users in diverseindustries to augment existing methods of monitoring, analyzing, andreporting the status of sensors and/or other measurement devices. Forthe purpose of this document, the software shall be referred to as theSoftware. We will also extend the analytic capabilities currentlyavailable to include advanced multivariate techniques and SCREAM (SystemCoherence Rendering Exception Analysis for Maintenance) techniques forprocess monitoring, control and optimization, fault & anomaly detection,the ability to identify key relationships between variables, and willreduce the complexity of control.

The Software will interface with existing process control hardware ande-enterprise software so that the results of the software's analyses canbe automatically translated into specific actions that improve plantefficiency. Although the software should be applicable to any industry,focus will be on the oil and gas, chemical, and consumer food sectors.Healthcare may also be an industry on which to focus.

In the present example, our system had one or more desirable features.These features include computer software that:

-   -   1. enables the collection of sensor data;    -   2. performs univariate, multivariate, and SCREAM analyses;    -   3. allows process models to be built and saved including an        interface to equation based, physical model builders; software        that monitors real-time sensor data;    -   4. allows data mining of historical and real-time data;    -   5. allows administration and configuration of users, sensors,        and data;    -   6. defines and manages alarms related to process model results;    -   7. provides expert systems to interpret alarm data and recommend        specific actions;    -   8. provides an interface to Enterprise Resource Planning (ERP)        systems that use process model results to initiate actions; and    -   9. provides an interface to Process Control systems that use        Process Model results to initiate actions.

As noted, the above are merely examples that should not unduly limit thescope of the claims herein. One of ordinary skill in the art wouldrecognize many other variations, modifications, and alternatives.

Project Description

The following have been identified as objectives for the Software: (1)decreasing the number of individual alarms a process operator needs toaddress; (2) reducing problem diagnosis time by providing sensitive androbust techniques for anomaly detection; (3) identifying systemattributes that can be optimized to save operating costs using advanceddata mining techniques; (4) providing system monitoring performanceallowing system monitors to exchange multiple univariate alarms forfewer multivariate or SCREAM alarms; (5) performing superior datapre-processing capabilities, data visualization, and flexible datapresentation; (6) reducing the amount of out-of-specification product,product re-working, and batch cycle times; and (7) reducing oreliminating catastrophic process events.

The problem is defined by demands on manufacturing processes that areconstantly rising, with higher targets of quality, throughput, and yieldbeing required at the same time as lower costs, less waste, and lesspollution. Meeting these demands necessitates better knowledge about theprocesses and process operations, as well as better control over processconditions.

Methods such as Principal Component Analysis (PCA) and Partial LeastSquares (PLS) work well for modeling and analysis of large and complexdata sets. These methods give easily interpretable results such asdeviations from the model. We believe that use of the JPL-developedSCREAM techniques can offer an even better way to detect, and ultimatelyresolve, faults even those for which models have not been explicitlytrained.

The scope of the project is characterized by a number of factors. Onesuch factor is geographical boundaries. For now, the product is beingdeveloped for the US market only. The system will be provided in Englishonly. While this does not have major development implications,development of alternate displays for numbers, etc. based on countryconvention (e.g., displaying 1.000.000 instead of 1,000,000) have notyet been undertaken. There may also be some implications for measurementunits (e.g., the use of liters vs. gallons, etc.)

Most of the testing done to date with SCREAM has been in the aerospaceindustry. JPL has reported success using these techniques, but theresults have not yet been verified in other industries. To address thisissue, we will work with potential partners during the software designphase to confirm the effectiveness of the SCREAM techniques in severalindustries.

Another possible factor is reluctance by management to adopt the system.With so much at stake on the manufacturing environment, management maybe reluctant to introduce an unproven product from a relatively smallplayer into their plant environment. To address this issue strategicpartnerships with a few high-profile partners will be pursued to developa track record of success for the product. In addition, the Softwarewill be deployed in parallel with existing techniques during a productvalidation period.

In addition, Model Builders may be reluctant to embrace another systemdue to the training required and the lack of perceived value. We need toaddress this issue by clearly demonstrating the value of the Softwareand getting Model Builders to view it as a must-have rather than anice-to-have.

Some research in the area of process control system suggests thatMonitor reluctance is a key reason why new software solutions are notreadily adopted into the normal work routine. To address this issue wewill focus resources during the design phase on a superior userinterface for users, with particular focus on the monitoring function.We will also focus on Monitor training during implementation. Monitorsmay need re-assurance that the Software is there to help them do theirjobs, not to displace them from their jobs.

Process control is a fairly crowded space with a few dominant players,but with many smaller players contributing subject matter expertise. TheSoftware will need careful positioning as a product that works withexisting software but that is good enough to stand on its own.

It will be important for us to develop/train internal resources tointegrate the Software with existing hardware and software in theprocess control environment. Alternatively, we could hire or contractfor appropriate resources in these areas.

We believe that a browser-based solution is crucial to the success ofthe product. It needs to be verified that that a browser-basedimplementation can achieve the performance requirements outlined in thisdocument. It is suggested that early measurements be made during thedesign phase to validate the technical feasibility.

A number of assumptions affect planning and project development.Detailed descriptions of assumptions that are underlying premises of theproject or system structure are described.

While outlined briefly here, it is expected that the Software willinclude an expert system that integrates with ERP systems and ProcessControl Systems. Systems should be designed with this -in mind, usingexisting industry standards wherever possible.

The Software will co-exist with process control and e-enterprisesoftware solutions already in place. It is assumed that some sort ofsoftware (i.e. a SCADA system) is already collecting, storing, andorganizing sensor data. Therefore, the Software will not need to beinteracting with the sensors directly.

JPL's SCREAM software is assumed to deliver the expected results andthat the technology is applicable to manufacturing environments.Furthermore, the Software will likely also integrate a software packagethat provides all univariate and multivariate calculations.

A number of assumptions concerning process control technology are givenbelow. First, the thin client HMI (Human Machine Interface) has becomemore pervasive in every aspect of both process and discretemanufacturing. Thin-client technology provides remote monitoring,control, and maintenance capabilities to Web-conceived machinery and canaccess server-based network applications and embedded devices with webserver software. Instead of the application residing and executing on alocal device, it resides and executes on the Web server. The Web servercan be resident on an internal high-speed intranet network or located onan Internet server anywhere in the world. Thin clients access HMIinformation using commercial Web browsers that do not require locallyresident HMI software. Web browsers provide thin-client technologyaccess to anyone who is authorized anywhere and anytime. Browsers bridgethe gap between diverse systems, are intuitive and easy to use, are freeor inexpensive, and run on PCs and Palmtops. They communicate with anycomputer embedded with Web server software, lower user training costs,and lower IT support and maintenance costs.

In addition, XML is emerging as the primary translation media for movingdata and information across the Internet. It will be used to movereal-time data from the device level to the enterprise level to runapplications that will provide the collaborative information neededacross all tiers within the factory and beyond. XML will become thequery-response format for many server applications.

XML schemas capture the essential data structures of the business andmanufacturing processes of vertical industry sectors and tradingpartners in the supply chain. Standardization of XML schemas replacesolder electronic data interchange (EDI) transaction data sets andestablishes, standardized supply chain data sets.

Furthermore, Java technology, which already is the preferred method ofpowering the Internet, will move to more and more controls applications.Its platform independence makes it a natural for use with heterogeneouslegacy systems. Implementation of e-manufacturing will be the primaryreason for using Java, since it was designed for highly distributedenvironments.

Java is the preferred implementation language for building browser-basedHMI front-ends to all manner of control systems connected across theIntranet/Internet. Embedded smart devices (drives, motors, servos,actuators, gauges, pumps, flow meters, etc.) will push data up from theplant floor to run everything from control to asset management and thesupply chain. Embedded Web servers will connect devices, controls, andsystems across the Internet to suppliers, subcontractors, and customers.

Wireless technology enables the mobile consulting, service, and supportthat is necessary in today's customer-driven economy. People are keptinformed, are always accessible, can respond quickly, and take actionremotely. Bluetooth is one wireless technology that will blossom in 2001as commercial handheld devices become available to support Bluetoothfunctionality in industrial equipment. Most of the early Bluetoothapplications will be in data transfer with moving machinery and MROfunctions.

Wireless LANs have been available for more than two years, but are justnow achieving high enough data rates and low enough selling prices to beconsidered for industrial automation applications. Early use of wirelessLANs has now replaced most new wired and RF data communications andhandheld data collection terminals in manufacturing, warehousing,shipping, and receiving. Improved antennas, roaming software, andincreased Ethernet network integrity coupled with lower hardware priceswill enable use of wireless LAN connections to movable shop floorcomputers.

Moreover, the emphasis of Web application hosting has migrated fromenterprise applications to the manufacturing arena. The use of the Webis allowing employees at all levels to manage plants and operations moreeffectively than ever before and at a lower cost. Collaborativesolutions that encompass facets of project management, process andproduct development, decision support, operational functions such asperformance monitoring and analysis, workflow control, asset management,process control, process optimization, and employee training are nowavailable. Although these solutions are available as standard products,the Web-hosted versions are gaining in popularity for a variety ofreasons including the inherent collaborative nature afforded with theInternet, a common user interface, and all of the advantages gained fromthe use of an ASP (Application Service Provider).

ARC expects new and innovative services to appear over the next year.For example, consulting services will play a major role in manufacturingin the near future. Instead of bringing consulting experts to thephysical location of your process or units, it is now possible, inprinciple, to bring the units to the consultant by providing access topertinent real-time data for analysis. Remote consulting will cover abroad spectrum including design, operational performance analysis,de-bottlenecking, process improvement, troubleshooting, and projectimplementation.

Another factor is the emergence of Publish/Subscribe (PIS) Technology.In a system that utilizes P/S, all stations operate as peers. Userssubscribe for the information they want at the frequency they need it.Sources of information publish information based on instruction fromusers, which eliminates bandwidth-consuming polling and high speedbroadcast techniques. From the emerging fieldbus networks to enterprisebusiness networks, P/S technology is a common thread and a consistentmechanism to move information.

Additionally, experiments recently revealed that P/S is a highlyefficient method for achieving multiple node time synchronization withlow network overhead. Time synchronization sufficient for processcontrol (tens of milliseconds) allows P/S to be used for synchronizationof control blocks in Foundation Fieldbus networks.

Product Definition

The Software will provide data -analysis capabilities and the ability todevelop process models for on-line monitoring. Data may be imported fromon-line or off-line databases, spreadsheets, physical models, or textfiles. These data are analyzed using statistical and graphicaltechniques to derive the appropriate models. The model and additionaldefault configuration information are then made available to theMonitoring System.

To use models for process monitoring, a model for the well-functioningprocess first needs to be developed from historical data. This model canthen be used to monitor the process in real-time. The followingfunctions are required for model definition and data mining:

-   -   1. Create a new process model;    -   2. Validate a process model;    -   3. Save a process model;    -   4. Modify a process model; and    -   5. Delete a process model.

Monitors need the ability to watch the health of their system. To dothis, the results of process models and individual sensors arecontinually monitored. Control charts are used to give Monitors agraphical view of a well or malfunctioning process and the presence orabsence of faults. A typical Monitor would watch one process model andseveral individual sensors simultaneously.

Once a sensor has been placed in a system view, it can be manipulatedwith the following functions:

-   -   1. Change Current (this session) & Default (future sessions)        View;    -   2. Change Current & Default Time Frame; and    -   3. Print View.

Once a process model has been placed in a system view, it can bemanipulated with the following functions:

-   -   1. Change Current (this session) & Default (future sessions)        View;    -   2. Change Current & Default Time Frame;    -   3. Enable/Disable Alarm Notification;    -   4. Examine individual analyses that comprise the model;    -   5. Print View.

Once the alarm monitor has been placed in a system view, it can bemanipulated with the following functions:

-   -   1. Change Current (this session) & Default (future sessions)        View;    -   2. Get Details of an Alarm;    -   3. Clear an Alarm;    -   4. Print Alarm Log; and    -   5. Log Alarms.

To organize the sensors, and models, and alarms that a Monitor can view,“system views” will be created. A system view is defined as a collectionof system statuses that a user has chosen to monitor. The followingfunctions are needed to set-up and maintain system views.

-   -   1. Create a New System View;    -   2. Add/Delete Content of a System View (e.g., What's in the        view);    -   3. Add/Delete a Sensor;    -   4. Add/Delete a Process Model;    -   5. Add/Delete the Alarm Monitor;    -   6. Modify Layout of a System View (e.g., Where the content        goes);    -   7. Modify the Colors/Backgrounds of a System View; and    -   8. Print System View.

All systems require some level of administration. The functions definedhere are required to administrate the Software's users and data. UserSet-Up Functions will allow an administrator to set-up and configureusers:

-   -   1. Add a User;    -   2. Disable a User;    -   3. Delete a User; and    -   4. Change Password.

User Functions enable users to get in and out of the system in a secureway:

-   -   1. Login;    -   2. Logout; and    -   3. Password Change.

Depending upon the design of the underlying data structures, Sensor DataFunctions may be required in order to make raw sensor data available tothe Software:

-   -   1. Add a sensor;    -   2. Delete a sensor; and    -   3. Configure sensor data.

Depending upon the design of the underlying data structures, Real-TimeData Functions may be required in order to get sensor data, provide thatdata to the data models, and after some period of time archive the data:

-   -   1. Get Sensor Data;    -   2. Provide Sensor Data to Models; and    -   3. Archive Data to Historical Server.

As with real-time data, historical data must also be made available tothe data models, and archived or deleted over time. Historical DataFunctions therefore serve to:

-   -   1. Provide Sensor Data to Models;    -   2. Archive Data to Storage Media; and    -   3. Delete Data

An expert system to interpret process model alarm data and recommendspecific actions for e-enterprise (ERP) systems and process controlsystems will be developed. The following are types of functions that anexpert system could provide:

-   -   1. Provide recommendations to Monitors about what to do to clear        a particular alarm (e.g., adjust sensor x to y);    -   2. Determine degradation over time in a system component (e.g.,        slow buildup of residue in a pump); and    -   3. Automatically provide information about a system component        that needs to be replaced to a SCM (Supply Chain Management)        sub-system.

An event-driven interface to Enterprise Resource Planning (ERP) systemsthat uses process model analysis data to initiate actions based on thoseanalyses will be provided. The ERP interface is expected to integratewith a variety of ERP systems, including but not limited to those ofSAP, IFS, Oracle Corp, J.D. Edwards, the Baan Co. Geac Computer Corp.,JBA International, i2 Technologies, The Foxboro Co./Invensys IntelligentAutomation, System Software Associate, and IBS.

An event driven interface to Process Control systems that uses processmodel analysis data to initiate actions based on those analyses willalso be provided. This interface will also be important for making gooduse of the detection of faults/anomalies data from SCREAM. The ProcessControl system interface will integrate with a number of process controlsystems, including but not limited to those of Honeywell,Fisher-Rosemount, Rockwell Automation, GE Fanuc, Siemens MooreProcessing Automation, Inc., Aspentech Technology, and the FoxboroCompany.

Functional Specifications

This section of the document describes the requirements for individualfunctions at a detailed level. FIG. 5 is a chart showing users of theSoftware.

One user group are the Model Builders. Model Builders create models torepresent the health or status of a system. Models can be simplecollections of individual sensors, or complex collections of sensors,other models, and virtual sensors. Models are at the core of theSoftware; they use raw sensor data to determine if the system is in orout of control, and provide that information to Monitors in the form ofcontrol charts and alarms.

A variety of functions are utilized for model building and data mining.One function is creation of a new model. Model Builders shall be able toa build process model. The overall flow for creating a process model isas follows:

-   -   1. Select algorithm;    -   2. Choose sensors (& other model input);    -   3. Select training data source;    -   4. Select training data start/end times;    -   5. Pre-process model data;    -   6. Define alarm conditions;    -   7. Validate model; and    -   8. Save model

Model Builders also shall select the algorithm and multivariatetechniques to be used in the model. A nonexclusive list of multivariatetechniques available to a user is shown below in TABLE 10. The ModelBuilder may also select one of the SCREAM techniques of TABLE 11 belowto be used in the model. If a SCREAM “continuous” data model is beingused, the Model Builder is allowed to import model result from anequation-based physical model.

A Model Builder also may choose sensors & other inputs to the model. Alist of available sensors may be displayed. Sensors may be describedeither by a description field, or by a naming convention that makes themeasy to identify.

Model Builders may also be able to select individual sensors, a group ofsensors related to a particular piece of equipment, or all sensors. Alist of other models may also be displayed. Model Builders shall be ableto select other models to include as input the model being built. Modelsshall be listed by “Model Name.” Models may contain multiple streams ofdata at a given point in time.

Model Builders may also select the source of the training data Trainingdata can come from a real-time data server, a historical data server, orfrom a Microsoft Excel spreadsheet. Model Builders may specify thelocation of the training data for each sensor or model that is used asinput to the model. If training data is being imported from an Excelspreadsheet, data fields from the spreadsheet may be mapped to theappropriate sensor. A function may be provided which enables the ModelBuilder to associate a sensor with a column of data in the spreadsheet.

Model Builders may also select the time period to be included in thetraining data. The user shall be able to select start and end date/timedown to the second (e.g., from MM/DD/YYYY HH:MM:SS to MM/DD/YYYYHH:MM:SS). Any valid dates may be entered.

The GUI may include pop-up calendars to aid the user in selecting thetime period. Users should be able to select dates from the pop upcalendars from today (no future dates) back to one year ago. Dates thatare not valid should not be selectable. Alternatively, users should beable to select month, day, and year from dropdown menus. Hours, minutes,and seconds should be entered on a 24-hour clock. Users should also beable to select hours, minutes, and seconds from drop down menus.

Model Builders may validate that data from the selected time period isavailable in the training data set for each sensor in the model. If thedata is not available for all sensors, Model Builders may: 1) select adifferent time period, delete the sensor from the model, or continue(pre-processing can fill in the missing data, although this is notrecommended).

Model Builders also pre-process model data. Training data may bepre-processed automatically to improve the quality of the input data.Pre-processing techniques are shown in TABLE 7. Available techniqueswill be selected. A Model Builder shall select one or more of the abovetechniques depending upon the choice of algorithm. Upon selectioncompletion, the training data should be run through the preprocessingtechniques selected.

Model Builders also have the ability to define conditions that triggeralarms. The detailed descriptions of the algorithms provided below showthe values can be used to create alarm conditions. Steps to create analarm condition are as follows.

-   -   1. Based on the algorithm used, display the list of variables        that can be evaluated to determine an alarm condition (e.g.,        Principal Component # 1, etc.).    -   2. The Model Builder shall build conditions consisting of one or        more variables (e.g., each alarm may contain up to five        variables. The variable to be evaluated should be selected from        a list. The operator to be used should be selected from a list        containing the following: greater than, less than, greater than        or equal to, less than or equal to, equal to, not equal to). The        user shall enter (i.e., not select) the actual value to be        tested:    -   e.g., ((x>5 and y<3)) or (z>7)    -   3. Up to ten different alarms can be defined per model. e.g.,        Alarm 1=x>5, Alarm 2 (x>5 and y<3), Alarm n=etc.    -   4. The Model Builder may associate a priority with an alarm        condition. There should be five different priority levels. The        priority levels should be: 1, 2, 3, 4, and 5, with five being        the most severe.    -   5. The Model Builder may specify which of the alarms are “on” by        default (that is, if the model were added to a system view,        which alarm notifications would automatically be enabled). The        Model Builder may also specify whether notification for this        alarm may be disabled by a Monitor.    -   6. The Model Builder may associate a 25-character text        description with an alarm condition.

The system shall automatically generate alarm conditions related to theupper and lower alarm thresholds for the algorithm. These alarms shouldonly be able to be edited by the Model Builder.

A Model Builder shall have the ability to validate a model by runningthe model against another set of data (either historical or real-time)to ensure that the model “works.” The following are the steps tovalidate a model:

-   -   1. Select the time period to be included in the validation data.        User should be able to select start and end date/time down to        the second (e.g., from MM/DD/YYYY HH:MM:SS to MM/DD/YYYY        HH:MM:SS).    -   2. Validate that data from the selected time period is available        for each sensor selected. Handle any errors.    -   3. Run the model against the validation data.    -   4. Present the results in the defaults defined for the model.

A Model Builder shall be able to save a model for personal use or foruse by others who may want to use the model. TABLE 1 shows some items tobe saved when a model is saved. TABLE 1 Items Saved with Model ChangeWithout Re- Data Name Description Comments Training? Model A designationof the model Used to know which unpublished Yes Creator creator. modelsbelong to a particular user. Model Name A descriptive name for the Amodel name can contain up to 25 Yes model. characters, including spaces.It cannot contain the following characters: \/: * ? “ <>|. Deplicatenames should not be allowed. Model A description of what the A modeldescription can contain up to Yes Description model does. 500characters. Any valid characters can be included. This description willbe used for help screens, and for describing the model when it is beingadded/deleted from system views. Sensors/Model The sensors and modelsused No Input Used as input to this model. Sensor/Model The loadings tobe applied to Applicable for some models. No Loadings each sensor/modelused in this model. The loadings are developed during model building.Pre-Processing The pre-processing techniques This may be from 0 to 10different No Techniques to be used when this model is techniques. run.Pre-Processing For each pre-processing Note the data varies depending onthe No Data technique used, store the technique. resulting output thatwas generated when the technique was run against the training data.These values will be needed when the model is run. Default Time Thedefault time frame to be Specified in minutes. Yes Frame used when thismodel is run (e.g., when the model is run use the last five minutes ofdata). Algorithm The algorithm to be used No when this model is run.Default View The default view for this Yes model (e.g., scatter plot).Default Time The default time scale for the Yes Scale for View defaultview. Data The rate at which data is For example, get data from all ofthe See Acquisition sampled from the data source. sensors required torun this model every Footnote¹ Rate 2.5 seconds. Data Display The rateat which data is For example, supply data back to the Yes Rate suppliedback to the user's user's display every 5 seconds. display. TrainingData The start date & time of the No Start Date & training data used tocreate Time this model. Training Data The end date time of the No EndDate & training data used to create Time this model. Training Data Theactual training data. Format may vary but most likely, along No list oftimestamps, sensor identifiers, and sensor readings. Alarm-Related Foreach alarm condition all of the Yes Data fields shown must be stored.Condition Condition: The condition that triggers the alarm (e.g., X > 5)Severity Severity: The severity of the error. From 1 to 5, 5 being mostsevere. Description Description: A short description of the alarm (e.g.,TC-125 Temperature High). Default Default Setting: Indicates if Settingthis alarm is enabled or disabled by default. Alarm Alarm Type:Indicates if this Type alarm is automatically generated by the model, orwas manually configured by the model builder. Disable? Disable?:Indicates if notification for this alarm can be disabled. Publish StatusIndicates if the model is Private models can only be seen/run by Yespublic or private the creator. Public models will be available foranyone to use.¹Varies by algorithm. In general, for state-based models (e.g., PLS,PCA) the answer is Yes. For dynamic-based models (e.g., SCREAM andMulti-Way PCA models), the answer is No.

Processes change over time. Sometimes, long-term changes in measurementconditions reveal the limited robustness of the initial model. This isparticularly the case for multivariate models that can be very sensitiveto small changes in sample conditions. As a result, Model Builders mayreplace or update models. A Model Builder may be presented with a listof all saved process models.

Models shall be displayed in alphabetical order by “Model Name.” Uponselection, the saved items in the model shall be displayed. When a ModelBuilder initiates a change to a published (i.e., public) model, a copyof the model is first saved with an “unpublished” (i.e., private)status. While the Model Builder is changing the model, the originalmodel is still published and available. When the model builder publishesthe changed model, the updated model should be used immediately uponpublication (i.e., if anyone has the model running, the new model shouldbe used immediately).

Some attributes of a model can simply be changed. Others, if changed,require the model to be re-trained and re-validated. TABLE 1 justpresented also indicates model data that can be changed without havingto re-train the model.

The Software further allows the Model Builder to select an attribute ofthe model to change. If one of the attributes that cause the model toneed to be re-trained is changed, when the model is saved, it should beconfirmed that- the model has been-re-trained and re-validated beforesaving. If the model has not been re-trained and revalidated, the useris required to do so before the model can be saved.

Model builders shall be able to import simulation results from aphysical 10 model The following steps input model results:

-   -   1. Using the physical model package, export the model results to        a spreadsheet. These requirements are not defined here. It is        assumed that he physical model software is able to export to a        spreadsheet.    -   2. Import spreadsheet data.    -   3. Assign process sensors to columns in the spreadsheet.

Models may become outdated or no longer required. The Software shallallow users to delete models. The Model Builder shall have the abilityto delete a model. The user may be presented with a list of all processmodels. One or more of the models are selected for deletion. Theselection process should follow the standard browser method of selectingone or multiple items from a list (e.g., “hold down the Ctrl key to-select multiple items”). If the model is public and the model has beenincluded in a system view, a warning message may be displayed to theModel Builder showing the number of views that include the model and areminder that deleting the model will delete the model from all systemviews. The user should be given the option to continue or cancel.

When a model is deleted, it should also be deleted from the system viewsof all users who have-it included in a view. However, if the model isrunning when it is deleted, the model should continue to run until thesystem view that used the model is closed. At that time, the modelshould be deleted from the view. When a model is deleted, all referencesto the model should be deleted from all user views, but the model shouldnot be deleted altogether from the system. This is done as an addedlevel of security to ensure that a model is not inadvertently deleted.This capability would allow the model to be restored. Individual userswho had included this model in their system views would however, need tore-add it to their views.

Once models have been created, they are run and the results aretypically presented to a Monitor who watches the health of the system.Model Builders can also perform all of the functions available toMonitors.

Configuration Functions allow Monitors who are watching a system todefine and manipulate what they see. Monitors shall be able to select a“Standard System View” to monitor. A system view is a one-screen viewcontaining sensors, models, and possibly other elements. A “StandardSystem View” represents a model builder's recommended set of models, andsensors to monitor for a given process. For example: a cereal plantmakes Fruit Loops, Cheerios, and Corn Flakes. Different unit operationsare used when making each type cereal. Fruit Loops require the dyemachine, the other -cereals do not. Corn Flakes require the toaster, theother cereals do not. A model builder can pre-define a “Fruit Loops”view that monitors only the unit operations used while making FruitLoops. This view includes the dye machine, other unit operations, andthe individual sensors for the food coloring supply tubes that tend toget clogged often.

Monitors shall also be able to create “Custom Systems Views.” Bydefault, all users will have at least one view, which is initially setto be the default view. The default view initially contains no content.The default view is automatically displayed when the user logs in. Forexample: Your job is to monitor the appliances in a house. Threedifferent views of the house could be set-up. One view might be theentire house with individual models monitoring each room. A second viewmight be only the kitchen with individual monitors for the dishwasher,the refrigerator, and the oven, etc. A third view might be only the airconditioning system throughout the entire house. The following stepscreate a new system view:

-   -   1. From an existing system view, select -an option to “Add a        System View” (or something like this); and    -   2. From this point, the user is directed to the Add/Delete        Content from a System View function.

Monitors shall be able to select content from a list of availablecomponents (sensors, process models, alarm monitors, and potentiallyother components), name the system view, and set the system view astheir default. Continuing the house example, say you just bought amicrowave oven. If there is a model that monitors your microwave oven,you could choose to add it to your kitchen view. Or if you install asmoke detector in the garage, that sensor could be added to the garageview. A user shall be able to add a number of components to be includedin a system view.

Monitors shall be able to add or delete a sensor from a Custom SystemView. Monitors are also able to display the sensors that can be added tothe Custom System View, and organize the sensor names in some logicalway. If technically feasible, display the sensors organized around theirphysical hierarchy, with the ability to expand or collapse thehierarchy. A graphic or iconographic view is highly desirable. Sensorsthat are already contained within the system view should be indicated assuch. A user may de-select (delete) a sensor. A Monitor may also selectone or multiple sensors for inclusion.

Monitors shall be able to add or delete a model from a Custom SystemView. The Software can display a list of all public models inalphabetical order by “Model Name.” Access to the “Model Description” isprovided to help the user to select the correct model. A graphic oriconographic view is highly desirable. Models that are already containedwithin the Custom System View should be indicated as such. A user mayde-select (delete) a model. The Software allows a Monitor to select oneor multiple models for inclusion. Once a model is added to a CustomSystem View, it immediately starts running with the defaultconfiguration saved with the model.

Monitors shall be able to add or delete the alarm monitor from a CustomSystem View. If the alarm monitor is already included in the CustomSystem View, the user is allowed to de-select (delete) the monitor. Oncea monitor is added to a Custom System View, it immediately startsrunning with the default configuration.

Monitors are able to assign a name to a Custom System View and to changethat name. By default, each new Custom System View is given the name“New View.” Enable the user to enter a name for the view. If the viewalready has a name, the user is allowed to change it. Names may containany character that a standard Windows file name may contain.

Users shall be able to designate a System View as their default view.The default view will automatically be displayed after the usersuccessfully logs into the system. If the designated default view isde-selected, make the first system view the default.

Model Builders shall be able to designate a system view as a StandardSystem View. Standard System Views will be made available to all usersto easily select a recommended set of models/sensors to be monitored fora given process.

The Layout of a System View may be modified to alter the position of thecontent. Monitors shall be able to reposition individual componentswithin a Custom System View. Although the specific design of thisfunction will depend on the GUI, it is envisioned that each modelmonitor, sensor monitor, and the alarm monitor will be roughly the samesize. Components should be able to be moved left to right or top tobottom (e.g., move Alarm Monitor above Sensor 1, or move Model 1 intoColumn 2).

The Colors/Backgrounds of a System View may be modified. Monitors shallbe able to select from up to five pre-defined skins to change the lookof their system views. Skins are templates that define the attributes ofthe display.

Monitors shall be able to use their browser's print function to printthe system view.

TABLE 2 describes a partial list of possible sensor types the Softwarecan monitor, along with the attributes of these sensor types. TABLE 2Sensor Types Measurement Sensor Type Description Options TemperatureTemperature “Temperature” is a Fahrenheit Kelvin [K] measurement ofdegree of hotness or [° F.] (Default) rankine (Rk) coldness measured ona definite Celsius [° C.] scale Pressure Pressure is a measurement offorce millibars pascals per unit area. bars (Default) atmosphereskilopascals inches of megapascals mercury mm of water inches of water mmof mercury feet of water kg/cm² pound/inch² tonnes/m² [psi] pounds/foot²Flow Rate Flow Rate is a measurement of the gallons/second centimeters³/(volume) amount of a liquid or gas that passes gallons/hour second afixed point in a given time. gallons/minute meter³/second foot³/secondmeter³/minute foot³/hour (Default) foot³/minute meter³/hourliters/second Speed Speed is a measure of the distance inches/seccentimeters/sec moved in a unit of time. inches/min (Default)inches/hour centimeters/min feet/sec meters/sec feet/min meters/minfeet/hour meters/hour miles/hour km/hour millimeters/sec Torque Torqueis a measure of the 1 bf feet kilonewton “strength” being used inturning (or 1 bf inches meters [kNm] attempting to turn) something. ozfinches kgf meters ton(UK)f feet kgf cm ton(US)f feet gramf cm newtonmeters tonnef meters [Nm] (Default) Acceleration Acceleration is ameasure of the inches/sec² miles/hour.sec rate at which a velocity ischanging. feet/sec² meters/sec² It may be positive (for increasing(Default) velocity) or negative (for decreasing miles/hour.minvelocity). Power Power is a measure of the rate of milliwatts btu/secdoing work (or using energy) in [mW] btu/min relation to time. Thestandard unit watts [W] btu/hour of power is the watt [symbol W],(Default) therms/hour which is a rate of 1 joule per second. kilowatts[kW] calories/sec megawatts calories/min [MW] kilocalories/sec terawatts[TW] kilocalories/min joules/sec kilocalories/hour kilojoules/minmegajoules/ hour Distance Distance is a measure of the space inches [″]centimeters [cm] between two points. feet [′] meters [m] yards (Default)miles kilometers [km] millimeters [mm] Discrete Discrete sensors can bein any of Open Type 1 several states. This sensor type Closed describesopen or closed. Discrete Discrete sensors can be in any of On Type 2several states. This sensor type Off describes on or off. DiscreteDiscrete sensors can be in any of 1, 2, 3, etc. Type 3 several states.This sensor type describes only a value (e.g., sensor is in state number2)

All sensors can be displayed using a Control, Shewhart, EWMA, or CUSUMchart. By default, data is displayed using a Control Chart. Severalfunctions are utilized to monitor sensors. When a system view containinga sensor is opened, all sensors in that view are displayed with theconfiguration saved with that system view, or with the sensor's defaultvalues.

A Monitor shall be able to select a sensor and change the look of thesensor display. The following items can be changed:

-   -   1. Time Scale: Changes the x-axis time scale. Enable user to        select from: 10 90 days, 30 d, 7 d, 1 d, 12 hours, 3 h, 1 h, 30        minutes, 10 m, 5 m, 1 m, 30 seconds, 10 s, 5 s, 2 s, 1 s, 500        milliseconds, 200 ms, 100 ms, 50 ms, 20 ms, 10 ms, 5 ms, 2 ms, 1        ms. Note this should not change the data acquisition rate or the        display rate; it merely changes the scale on which the available        data is drawn.    -   2. Minimum/Maximum Values: Changes whether the minimum and        maximum values (since sensor monitoring was started) are        displayed.    -   3. Show Samples: Changes whether or not the chart includes tic        marks to indicate when samples were taken (e.g., if display        scale is every 500 ms, but you only get data every 1 second, one        tic mark would be displayed in every other time scale unit.    -   4. Show Alarm Threshold Limits: Changes whether or not alarm        threshold limits are displayed (if they are available).    -   5. AutoScale: Changes axis scaling so that smallest and largest        values are at the bottom and top (or left and right) of the        plot, respectively.

Monitors shall have the ability to specify the time from when the sensorshould begin monitoring. The user shall indicate if the change is forthis monitoring session only, or whether this change should beremembered for future. When a sensor is “opened” (e.g., displayed in asystem view), the data is displayed from a point in time based on eitherthis user's defined preference, or the “Default Time Frame” stored withthe sensor if the user has not defined a preference. The user shouldselect the starting time relative to the current time, and specify thetime in hours and minutes. If the time period chosen is earlier than thetime. the current sensor was opened, the sensor data must be calculatedfrom the starting point to the present, using the set refresh rate (therate at which the model normally updates).

The Print View allows monitors to use their browser's print function toprint the system view. No special requirements.

Monitors shall have the ability to save the system view (i.e., thegraphical view) in a file. The system view should be saved in a standardgraphic form for easy input into a MS Office document (e.g., Word,PowerPoint, etc.).

When a system view containing a model is opened, all models in the vieware displayed with the configuration saved with that system view or withthe model's defaults. The Software enables examination of individualanalyses comprising the model.

Monitors shall be able to click on any individual point in a model toget additional detail. When an individual point is selected, anappropriate graph/plot for that point should be opened in a separatebrowser window. The next chart to be displayed will vary depending onthe analysis being viewed, and the level of the chart being viewed. Inorder to change current & default time frame, the requirements are thesame for models as they are for sensors.

Monitors shall have the ability to enable/disable notification for amodel's alarms. The process to enable/disable alarm notification is asfollows:

-   -   1. Display a list of the available “Alarm Conditions” from the        stored model data.    -   2. Users shall not be permitted to disable any of the        “automatic” alarm conditions that have been defined by the Model        Builder, or alarms that have been defined by the Model Builder        as “not able to be disabled”.    -   3. Alarms that are already enabled should be indicated as such.        Allow user to disable an alarm. Allow user to enable one or more        alarms.    -   4. The software should confirm the alarms have been successfully        enabled or disabled. Disabling alarm notification does not        disable the alarm. The alarm still gets logged, but the Monitor        simply does not get notified that the alarm occurred.

Alarms can be viewed in two ways. In each model view, there will be somesort of alarm status monitor that displays whether that particular modelis in an alarm state. The Software will also provide the ability tomonitor all of the alarms from any running model in a single alarmmonitor view. Alarms are enabled or disabled in the model view not thealarm monitor view.

When a model is running, alarms may be generated by that model and byany model used by that model. The same alarm should be reported onlyonce by a model. For example, if the model updates every second and thesame alarm condition is present every second, the alarm should only bereported once. However, once the alarm has been cleared, if the alarmcondition is still occurring, the alarm should be reported again.

Monitors shall be able to see the alarm status of an individual model.Some sort of graphic or icon should communicate the model's alarmstatus. If no alarms are currently tripped, this should also becommunicated. If an alarm is tripped, the display should indicate theseverity of the alarm, and the “Alarm Description” should be displayed.For example: A traffic signal is chosen to represent alarm status. If noalarms are tripped, the light is green. If a severity 4 or 5 alarm istripped, a red light is displayed. If a severity 1, 2, or 3 alarm istripped, a yellow light is displayed. Inmost cases, the alarmdescription would scroll across the bottom of the traffic signal.

Monitors shall also be able to see alarms generated by all the models inthe System View in a single list. For each alarm, the alarm date, time,severity, and “Alarm Description” should be displayed. Alarms should bedisplayed in chronological order with the most recent alarms displayedat the top of the list. If multiple alarms with the same date and timehave occurred, the alarms should be further sorted by severity. Forexample: Date Time Severity Description Jan. 22, 2001 05:36:20 Severity#5 TC-125 Puffer Clogged Jan. 22, 2001 05:30:22 Severity #3 TA-300Temperature High Jan. 22, 2001 04:22:01 Severity #2 DM-425 Red Dye#2 Low

A Monitor shall be able to get the details of an alarm. Alarms displayedin either the alarm monitor or the model view should be “clickable” toget additional information about the alarm. When clicked; the window ofthe model that generated the alarm should be opened. A text descriptionof the alarm will display and in the future, possible corrective actionswill also be displayed.

Monitors shall have the ability to “clear” alarms from the alarm monitordisplay. Users should indicate which alarms should be deleted. A “ClearAll” function should also be provided to clear all alarms in oneoperation. Clearing an alarm in the alarm monitor should also clear thealarm in the model view. The system should log the time an alarm wascleared and the Username of the user that cleared the alarm. Alarmsshould have some sort of unique identifier. A user should be able toclearly determine from log analysis, each unique occurrence of an error,and at what time each user(s) cleared the alarm.

Users shall have the ability to review historical information about thealarms that have occurred. Alarms generated by any models in the activesystem view should be logged. Alarms should be logged regardless ofwhether alarm notification is enabled or disabled (i.e., all alarmsshould be logged even if the user has chosen to be notified of Severity5 errors only). All the data that is displayed should also be logged. Inaddition, the model and/or sensor that generated the alarm should alsobe logged. Log files should be stored locally on the user's machine.Each time a user opens a system view, a new log file should be created.Logs should be kept on the user's machine for 30 days. Log files olderthan 30 days may automatically be deleted.

The file naming convention should be indicative of the system view name,the time, and the date (e.g., 01-15-01 09:35:02 My House Log) so thatthe log files can be easily identified. Log files should be stored in astandard file format (e.g., CSV—Comma Separated Value) for easy importinto database or spreadsheet programs. Alarms should also be logged in acentral location. The same logging requirements apply to the logs keptat a central location. However, alarms should be stored by the modelthat generated the alarm rather than by system view.

Users shall be able to use the Windows Notepad program to open, view,and print the locally stored log files.

A variety of functions are utilized to administrate the Software's usersand data. User Set-Up Functions allow an administrator to set-up andconfigure users.

Administrators shall be able to add new user to the system. Associatedwith each user will be a User name, a Password, and a User Type. When anadministrator adds a user to the system, the desired User Name and aninitial password are entered. The user is required to change the initialpassword during the first log in.

At least three different user types are currently envisioned:Administrators, Model Builders, and Monitors. FIG. 5 describes thefunctions available to each type of user.

Administrators shall be able to disable a user login. This will notaffect the views or models the user has stored, but it should block thatuser from logging in.

Administrators shall be able to delete a user. Deleting a user does notdelete any models that user may have created. Custom System Viewsassociated with that user should be deleted when the user is deleted.

Administrators also need to be able to manage passwords. Users forgetpasswords. Administrators shall be able to reset a password for a Username to any initial password. The user is required to change the initialpassword during the first log in.

Several functions enable users to get in and out of the system in asecure way. In order to Login, users shall enter a User name and aPassword in order to gain access to the system. The user is required tochange the initial password during the first log in. Upon successfulentry and validation of a password, users will be directed to a defaultpage. Once a user logs in, that login session will be valid until: 1)the user chooses to logout, 2) the browser window is closed, or 3) aperiod of one hour elapses with no activity.

Users shall be able to logout from any screen. Upon logout all models,sensors, and alarms running in any active views for this user should bestopped.

Users shall be able to change the password associated with their Username. To change a password, a user must first login to the system usingthe procedure outlined above. To change a password, the user must enterthe current password, and the new password twice (to ensure it wasentered correctly). The new password is validated for validity (validcharacter check only), and if valid, is updated. If the passwordcontains invalid characters, an error message is displayed and the useris given the option to try a different new password.

Depending upon the design of the underlying data structures, Sensor DataFunctions may be required in order to make the sensor raw data availableto model builders. An administrator shall be able to add a sensor to theSoftware. Adding a sensor will make that sensor's data available tomodel builders and system monitors TABLE 2A shows the data required toadd a sensor. Administrators shall be able to import the list of sensorsfrom a spreadsheet. This will facilitate the initial set-up of theSoftware. TABLE 2A Sensor Data Data Name Description Comments Sensor Asensor name can contain up to 25 Name characters, including spaces. Itcannot contain the following characters: \ /*?”<>ξ. Duplicate namesshould not be allowed. Sensor Where models should obtain the Data rawdata from when using this Location sensor. Sensor A description of whatthe sensor A sensor description can contain up to Description does. 500characters. Any valid characters can be included. This description willbe used for help screens, and for describing the sensor when it is beingadded/deleted from system views. Sensor Type The type of sensor. SeeTABLE 2 for a list of sensor types. Measurement The unit of measure usedin the One of the Measurement Options Unit raw sensor data. defined inTABLE 2. Default The default units in which the One of the MeasurementOptions Display sensor value should be displayed defined in TABLE 2.Unit. to the user. If the Default Display Unit is different from theMeasurement Unit, a conversion needs to occur Default The default timeframe to be used Specified in minutes. Time when this sensor isdisplayed (e.g., Frame upon initial display, show the last five minutesof data). Default The default view for this sensor One of the ValidViews defined in View (e.g., strip chart). TABLE 2. Data The rate atwhich data is sampled For example, get data for this sensor Acquisitionfrom the data source. every 2.5 seconds. Rate Data The rate at whichdata is supplied For example, supply data to the user's Display to theuser's display. display every 5 seconds. Rate

Administrators shall be able to delete a sensor from the Software.“Deleting” a sensor in affect, stops the collection of that sensor'sdata and makes the sensor unavailable for use in monitoring views andmodels. Steps to delete a sensor are as follows:

-   -   1. Display a list of the sensors that have been configured.        Select the sensors to be deleted.    -   2. The software should check if the sensor is used in any        models. If a sensor is used in a model, the administrator should        not be able to delete the sensor. The software should display a        list of the models that use the sensor, and the creators of        those models. All models that use the sensor must be deleted        prior to the deletion of the sensor. Sensors can be deleted even        if they are included in System Views.    -   3. The software should confirm the successful deletion of the        sensors.

Similar to the add function, Administrators shall be able to change theinformation about a sensor. Changing defaults will affect all usersexcept those users that have explicitly over-ridden default values.

A number of overall system requirements have been identified. TheSoftware should be accessible from any Windows PC equipped with anappropriate browser, such as Microsoft Internet Explorer and Netscape4.5+ family of browsers.

Minimum hardware requirements are the same as the minimum requirementsto run the I.E. 5.0. They are a 486DX166 MHz or higher computerprocessor. A Windows 95, Windows 98, or Windows NT 4.0 (SP 3 or higher)operating system. 16 MB (megabytes) of RAM for Windows 95 and Windows98:; for Windows NT: 32 MB of RAM. 70 MB Hard Drive Space for install,55 MB Required to run after restart.

The following have been identified as help requirements. The Softwareshould make use of screen tips. These are text descriptions that appearwhen the cursor is hovered over a selection. Links should be availablefor short descriptions to long descriptions (e.g., if short model namesare displayed for selection, an extended description should be availablevia hyperlink (perhaps in a pop-up window). Help should be available formost Software screen displays. In general, help screens should explainthe available functions on the screen, and describe theoutputs/displays. A user manual shall be provided with sections forModel Builders, Monitors, and System Administrator functions.

The following have been identified as security requirements. Passwordsare not displayed or printed. Upon entry, password characters should bemasked with asterisks. Passwords should be stored encrypted. If a userforgets a password, an administrator should reset the password and theuser should be forced to do a password change upon next login. Acapability must exist for encrypting data for certain sessions. If auser logs into the system from outside some pre-defined network space,all data transmitted to and from that user should be encrypted. Allsystem access should be recorded. Time, Date, and Username, and userlocation (IP Address) should be recorded for each login and logout ofthe system. Both successful and unsuccessful login attempts should berecorded.

Operations Environment

The following operations environment requirements have been identified.

Inputs for the Software will be different based on where the software isbeing installed. At a high level, we can describe the input of thesystem to be Sensor Data or Model Data. The Software is primarilyconcerned with the streaming and analysis of real-time data. Themonitoring tools will be important to the product. There are no specificrequirements as to the exact look of the screen displays to bedeveloped. These will be developed during the detailed design phase.

It is recommended that a prototype of the system be developed in concertwith users familiar with both the needs of Model Builders and Monitors.This could be done via either qualitative testing with an actualprototype, or through focus groups with select groups of users (e.g.,Monitors) using mock-ups of screens.

The following have been identified as MIS requirements. The Softwareshall provide a report of the alarms that have been generated for agiven date/time range. All of the data logged for the alarms, includinginformation about who cleared the alarms should be included. TheSoftware shall provide a report of everyone who accessed the system fora given range of dates/times. Unsuccessful login attempts should also beincluded. The Software shall provide a report of the sensors that haveconfigured. The report may include all of the information of TABLE 2A.The Software shall provide a report of the models that have beencreated. The report may include the information in TABLE 1.

Calculations will be required for the techniques described in TABLE 7(Pre-Processing Techniques), TABLE 8 (Univariate Techniques), TABLE 10(Multivariate Techniques), and TABLE 11 (SCREAM Techniques).

Interaction with OPC Servers will be the primary systems with which theSoftware will interface. OPC Servers will provide virtually all of theraw sensor data to the Software. If an OPC is not in place at a customersite, the Software deployment will need to include the installation andconfiguration of such a server. The Software will interface with ERPsystems and process control systems.

Certain processing and service standards and standards are needed tomeet the applicable objectives stated in the project objectives sectionand in the Statement of Work. Factoring in cost considerations, somestandards have been deemed “nice to have” rather than critical.

Calculations may be accurate to six or fewer decimal places using singleprecision. By default, all numbers may be displayed rounded to foursignificant digits. Since not all of the Software will be developed atthe same time, the implementation must allow for additional systemcomponents to be added easily in a modular fashion. Ideally, new systemcomponents should be able to be added without recompiling or changingthe GUI. It is expected that the following will be the subject ofmodules:

-   -   1. Pre-Processing Techniques;    -   2. Univariate Algorithms;    -   3. Multivariate Algorithms;    -   4. SCREAM Algorithms;    -   5. Charts/Plots;    -   6. An Expert System; and    -   7. Interfaces to ERP and Process Control Systems.

It is estimated that approximately or fewer Monitors will be using thesystem at any given time, and that the Monitors will monitor a subset ofthe same process data. In one example, a subset of process data isapproximately forty-four individual sensors and twenty models, with eachmodel containing approximately seventy-five individual sensors.Therefore, in this example the Software should be able to process rawdata from approximately 1,500 sensors, using the data from those sensorsto feed twenty models. These calculations may be performed once everysecond.

As manufacturing plants are often in continuous operation, the Softwareshould strive for 100% availability. The system should be structuredsuch that it can run for weeks in an unattended mode. Since the Softwarewill likely not be initially be used to actually control manufacturingprocesses, initial system availability may exceed 99.35% (no more than10 minutes of downtime per 24-hour period), assuming 100% availabilityof the data sources.

Once the Software is actually implemented to control processes, theSoftware will interface with the actual process control systems. In thisscenario, a more stringent system availability is required. For thislatter phase of implementation, system availability may exceed 99.998%(no more than 1 hour of downtime per 30-day period). A system viewcontaining 4 sensors and 4 models may take no longer than 1 second toupdate.

Appendices

TABLE 3 describes different types of plots that may be supported bySoftware. TABLE 3 Plot Types Name Description Line Plot A time series ortrend chart examines the time-dependent behavior of a sensor by plottingthe value of the sensor as a function of time. Scatter A 2D ScatterDiagram examines the relationships between data collected Plot (2D) fortwo different characteristics. Although the Scatter Diagram cannotdetermine the cause of such a relationship, it can show whether or notsuch a relationship exists, and if so, just how strong it is. Theanalysis produced by the Scatter Diagram is called Regression Analysis.Scatter A 3D Scatter Diagram examines the relationships between datacollected Plot (3D) for three different characteristics. Density Adensity plot is a two-dimensional grid with a defined number of Plotincrements for each of the two axes—the bottom and left-hand sides ofthe grid. The number of increments for each axis may be unequalin-general, but will typically be the same for this work. The grid linescould be shown but will not be shown here. To generate a density plot,three numbers are required: (1) the grid location on the bottom axis,(2) the grid location on the left axis, and (3) the value associatedwith the grid point. The value of the grid point determines the color tobe shown in the grid via a lookup table or mapping function.. Bar ChartA bar chart is typically used to show the numerical values associatedwith a series of qualitative variables. Rather than showing the valuesas points or lines between points, a rectangular box is drawn betweenthe point and a value of zero for each of the values. In this work,two-dimensional bar charts will be used and described. Typically, thebottom axis is reserved for the qualitative variables (e.g., sensorname, year) and the left axis is used for the quantitative value (e.g.,contribution). Dendogram A tree diagram is used to graphically displaythe hierarchy and relationships amongst objects/samples. The distancefrom the beginning (where all samples are separate) to the junctionbetween two or more samples or groups is a measure of the dissimilaritybetween samples or groups of samples.

TABLE 4 plots attributes of the plots of TABLE 3. Attributes refer tothe way in which a plot is displayed to the user and those things thatthe user may change in the plot. The user should be able to rotate the3-D scatter plot. TABLE 4 Plot Attributes Turn Draw Draw Display GridLines Symbols for Labels for Set/ On/Off Show Colors Plot Between EachEach AutoScale (Major Alarm Aspect Plot (fore/background, Name VariablesPoints? Point? Point? Axes? Axes)? Limits Ratio? Size? etc.)? Line Plotx, y Yes User Defined No User Defined User User User User User DefinedDefault: No Default: Defined Defined Defined Defined AutoScale Default:Default: Default: Off Yes 1.6 Scatter Plot x, y No Yes User User DefinedUser No User User User Defined (2D) Defined Default: Defined DefinedDefined Default: AutoScale Default: Default: Yes Off 1.6 Scatter Plot x,y, z No Yes User User Defined Off No User User User Defined (3D) DefinedDefault: Defined Defined Default: AutoScale Default: Yes 1.6 Density x,y N/a N/A N/A N/A N/A N/A User User User Defined Plot Defined DefinedDefault: 1.0 Bar Chart x, y No No No User Defined User User User UserUser Defined Default: Defined Defined Defined Defined AutoScale Default:Default: Default: Off yes 1.6 Dendogram N/A N/A N/A N/A N/A N/A N/A NoUser User Defined Defined

TABLE 5 describes some chart types supported in the Software. TABLE 5Chart Types Name Description Control Chart A control chart is used tovisually verify whether a given sensor is within pre-defined controllimits. It is a trend chart with horizontal lines for the mean (or setpoint), upper control limit and lower control limit for that particularsensor. Shewhart Plot Control charts. EWMA An EWMA (ExponentiallyWeighted Moving-Average) (Exponentially Chart is a control chart forvariables data (data that is both Weighted Moving- quantitative andcontinuous in measurement, such as a Average) measured dimension ortime). It plots weighted moving average values. A weighting factor ischosen by the user to determine how older data points affect the meanvalue compared to more recent ones. Because the EWMA Chart usesinformation from all samples, it detects much smaller process shiftsthan a normal control chart would. CUSUM A CUSUM chart is a controlchart for variables data that (Cumulative Sum) plots the cumulative sumof the deviations from a target. Because each plotted point on the CuSum Chart uses information from all prior samples, it detects muchsmaller process shifts than a normal control chart would. Hotelling T²The Hotelling T²-statistic measures unusual variability within thecalibration model space. Q-Residual Companion plot to Hotelling T²versus time. The Q-Residual statistic is the sum of squares of theerrors between the data and its estimates and is a measure of the modelmismatch. SPE (Squared The Squared Prediction Error (SPE) chart may alsobe used Prediction Error) to detect shifts. The SPE is typicallyassociated with PLS rather than PCA. Coherence Difference The CoherenceDifference Matrix Norm chart is used by the Matrix Norm Coherence-BasedFault Detection portion of SCREAM for identifying faults and processstates. Pareto Chart A Pareto Chart is a vertical bar graph showingproblems in a prioritized order, so it can be determined which problemsshould be tackled first. Histogram A single response (measurement,variable) is divided into a series of intervals, usually of equallength. The data are displayed as a series of vertical bars whoseheights indicate the number of data values in each interval.Contribution Plot The value of the loading for each of the sensors forone (Scores) component in a model. The component to be plotted is chosenby the user. If the first principal component in a PCA model is chosen,the contribution plot will be a bar chart showing the loadings (whichhave positive and negative values) for PC#1 for each of the variablesused in the model. Contribution Plot When calculating the value of T²,Q-residual or SPE for new (Errors) data for a model that has beenpreviously built, each sensor has a non-negative contribution. Thecontribution plot shows the value of the contribution for each of thesensors in this calculation. Scores Plot The Scores plot shows thedistribution of the samples in the model. Loadings Plot Loading Chartsprovide an indication of the relative contribution of each ProcessVariable towards a given Principal Component for all groups in theanalysis. Parallel Coordinate By representing each observation not as apoint in a scatter Plot plot but as a series of unbroken line segmentsconnecting parallel axes. Each axis represents a different variable.Coherence Chart A square checkerboard plot (or density plot). The numbersquares along one side equals the number of sensors. The color of thebox is related to the degree of covariance between two sensors. Thediagonal elements always have the color associated with a value of unitysince a sensor is perfectly correlated with itself. The Coherence Chartis used by the Coherence-Based Fault Detection portion of SCREAM toidentify relationships between sensors. Coherence Difference TheCoherence Difference Chart is used to visualize a change Chart from anexpected process state. If the current state is identical to theexpected process state, the entire chart will be black (e.g., nodifference). Colors appear as differences are detected. If only a singlebox is a different color, this indicates a change in the coherencebetween two sensors. (The identity of these sensors can be determined bylooking at the axes.) If an entire line is a different color and cross-hairs are visible, this indicates a change in the coherence between onesensors and all other sensors in the sub-system.

Table 6 describes the contents of the chart types of TABLE 5. TABLE 6Chart Contents Variables Name Plot Type X y z, ρ User-Selected OptionsShow Alarm? Control Chart Line Plot Time Sensor value N/A y If DefinedShewhart Plot Line Plot Time Sensor value N/A y If Defined EWMA(Exponentially Weighted Line Plot Time Sensor value N/A y If DefinedMoving-Average) CUSUM Line Plot Time Sensor value N/A y If Defined(Cumulative Sum) Hotelling T² Line Plot Time Hotelling T² N/A Model YesQ-Residual Line Plot Time Q-Residual N/A Model Yes SPE (SquaredPrediction Error) Line Plot Time SPE N/A Model Yes Coherence DifferenceMatrix Line Plot Time Matrix norm N/A Model Yes Norm Pareto Chart BarChart Variable Name Number of N/A Condition None Occurrences HistogramBar Chart Value Number of N/A Variable None Occurrences ContributionPlot (Scores) Bar Chart Variable Value (PC #) N/A Point in Scores YesName/Number Plot; PC Number Contribution Plot (Errors) Bar ChartVariable Value (T², Q, N/A Point in T², Q, Yes Name/Number SPE) SPE PlotScores Plot Scatter Plot (2D, 3D) PC², Time PC PC x, y, z None LoadingsPlot Scatter Plot (2D, 3D) PC², Time PC PC x, y, z None ParallelCoordinate Plot Line Plot PC Number Value of N/A Model NoneCorresponding PC Coherence Chart Density Plot Variable Sensor CoherenceModel Subsystem None Name/Number Name/Number²PC = Principal Component.

TABLE 7 shows some data pre-processing techniques. For each technique,the required inputs, expected outputs, and information stored with themodel are defined. TABLE 7 Pre-Processing Techniques Pre-ProcessingTechnique Name Pre-Processing Technique Description Data Centering andEliminates the units associated with different measurements Scaling(auto- (e.g., temperature, pressure) and scales the data by the scaling)variance so that all sensor responses are approximately the same scale(e.g., typically between −3 and 3) is required for PCA and PLS but isnot required for SCREAM elements. Data This feature specifically targetstime lags between different Synchronization sensors during dataacquisition and uses a buffer to match time stamps (as closely aspossible) for different sensors/systems. Data Transformation/ Atransform is applied to the data to eliminate effects such asLinearization seasonal trends and/or transform the data into a linearform. Elimination of A useful technique to reduce computation time ifRedundant Variables computation time becomes an issue during the designphase of the project. Estimation of Data for one sensor may be missingfor a variety of reasons Missing Data (e.g., sensor removed, sensor notpolled, reading not properly transmitted). A scheme must be developedfor estimating the value of this sensor in order to use PCA or PLSmodels. Noise Filtering Techniques (e.g., Savitzky-Golay, exponentialmoving average) to reduce the effects of noise. If the noisecharacteristics of the sensor change, most noise filtering techniqueswill not remove these characteristics. Thus, the noise model in SCREAMfor anomaly detection is still valid even after noise filtering. OutlierDetection This step is used during model building but not whilemonitoring. An “outlier” is a point that is statistically quitedifferent from all other points. Outliers must be removed during modelbuilding to obtain a good estimate of normal operations. VariableSelection Related to elimination of redundant variables. The purpose ofthis technique is to quickly screen the sensors and determine which ofthese sensors are the most significant without having to build a complexmodel and calculate loadings.

Data centering and scaling are used when building PCA or PLS models.Auto-scaling for multi-way PCA is not as straightforward as typicaltwo-dimensional PCA models. Inputs During Model Building are sensorreadings over time. Expected Outputs During Model Building areauto-scaled sensor readings over time. Information Saved with Model areaverage and standard deviation for each sensor for all data used tobuild the model. Inputs During Model Monitoring are sensor readings overtime and average and standard deviation for each sensor for all dataused to build the model (from information saved). Expected OutputsDuring Model Monitoring are auto-scaled sensor readings over time, basedon the auto-scaling parameters used to build the model.

Data synchronization is important when acquiring data from multiplesystems in multiple locations. When linked directly to a single OPCserver, data synchronization may not be an issue. Typically a buffer isused to acquire data. Inputs during model building are sensor readingsover time. Expected outputs during model building are sensor readingsover time so that time stamps for all sensors types are approximatelyequal. Inputs during model monitoring are sensor readings over time.Expected Outputs During Model Monitoring are sensor readings over timeso that time stamps for all sensors types are approximately equal.

Missing data has an important effect on the analysis for certain models.If data is missing for either a PCA or PLS model and. the loading islarge enough, then the model will produce meaningless results. Theeffect of missing data is riot nearly as vital for the algorithms ofSCREAM, and missing data may not be estimated- nor replaced for SCREAMmodels.

If there is a missing value for a PCA or PLS model, there are three waysto handle the issue:

-   -   1. Do not include data for analysis when there are missing        values. If the problem persists, report an error.    -   2. If the problem persists and cannot be fixed, build a new        model that doesn't include the sensor(s) with missing values.    -   3. Estimate the value (e.g., use an average value, use the prior        value, use a PLS model and inherent redundancy in subsystem,        etc.). If the problem persists, report an error.

Where missing values are to be replaced, inputs during model buildinginclude sensor readings over time. Expected outputs during modelbuilding are sensor readings over time with missing values replaced.Required inputs during model monitoring include sensor readings overtime. Expected outputs during model monitoring include sensor readingsover time with missing values replaced.

The purpose of noise filtering is to eliminate spikes and not change thestructure of the underlying noise. Inputs during model building includesensor readings over time. Expected outputs during model buildinginclude sensor readings over time after noise filtering. Parameterssaved with a model are not specific to a model but are universal. Inputsduring model monitoring include sensor readings over time. Expectedoutputs during model monitoring include sensor readings over time afternoise filtering.

TABLE 8 shows various univariate techniques. TABLE 8 UnivariateTechniques Univariate Technique Name Average Univariate TechniqueDescription Average The arithmetic mean gained by adding two or morequantities and then dividing by the total number of quantities. StandardDeviation A statistical measure of how widely individual items in afrequency distribution differ from the mean. Capability Index (Cp) Ameasure of the ability of the process to make product withinspecification. Defined as: (high spec − low spec)/(6 * sigma), wheresigma is the measured standard deviation. Upper Capability Index (Cp, u)Defined as: (average value − lower spec)/(3 * sigma) Lower CapabilityIndex (Cp, Defined as: (high spec − average value)/(3 * sigma) 1)Capability Index 2 (Cp, m) Accounts for deviation from a target value.Defined as: Cp/sqrt(1 + (average − target)²/sigma²) Instability Index(St) Used to examine the stability or instability of a process overtime. Defined as: (Number of out-of-control data points ÷ Total numberof data points) × 100

For the univariate techniques shown in TABLE 8, TABLE 9 describes therequired inputs and expected outputs. TABLE 9 Inputs And Outputs ForUnivariate Techniques Univariate Technique Name Inputs Expected OutputsAverage Sensor reading over time Average Standard Deviation Sensorreading over time Standard Deviation Capability Index High SpecificationCp (Capability Index) (Cp) Low Specification Standard Deviation UpperCapability Average Value Cp, u (Upper Index (Cp, u) Low SpecificationCapability Index) Standard-Deviation Lower Capability Average Value Cp,1 (Lower Index (Cp, 1) High Specification Capability Index) StandardDeviation Capability Index 2 Cp (Capability Index) Cp, m (Capability(Cp, m) Average Value Index 2) Target Value Standard DeviationInstability Index # of Out of Control Points St (Instability Index) (St)Total # of Control Points

TABLE 10 shows some of the multivariate techniques expected to beemployed in conjunction with the Software. TABLE 10 MultivariateTechniques Multivariate Technique Name Multivariate TechniqueDescription ACE (Alternating A multivariate non-parametric regressionConditional Expectations) procedure where the objective is identical tothe Additive Model (AM) but extends the capabilities of AM by allowing afunctional transformation of the response variable as well as theexplanatory variables. AM (Additive Model) A multivariate non-parametricregression procedure that finds sets of functions to transform theexplanatory variables to maximize the correlation between thetransformed explanatory variables and the response variable. AVAS(Additivity and A multivariate non-parametric regression VarianceStabilization) procedure that is an extension of Alternating ConditionalExpectations (ACE) and imposes variance-stabilizing transformations. CDA(Canonical CDA is one of the algorithms in the larger class ofDiscriminant Analysis) discriminant algorithms that is a subset offactor analysis. A discriminant algorithm requires supervised learningand each class is known and appropriately labeled. Discriminantalgorithms calculate the loadings to maximize the variance betweenclasses. CLS (Classical Least A method of multivariate calibration. ACLS Squares) model assumes the form X = CS + E, where X is the responsedata, S is a matrix of pure component responses, C is a matrix ofweights (concentrations) and E is a noise or error matrix. An estimateof S is calculated by (C^(t)C)⁻¹C^(t)X. Genetic Algorithms Searchprocedures that use the mechanics of natural selection and naturalgenetics. The basic operation of a genetic algorithm is simple. First apopulation of possible solutions to a problem is developed. Next, thebetter solutions are recombined with each other to form some newsolutions. Finally the new solutions are used to replace the poorer ofthe original solutions and the process is repeated. HCA (HierarchicalCluster HCA is one of the algorithms in the larger class of Analysis)cluster analysis. Classification is accomplished in an unsupervised mode(based on distances/similarities) and the results are shown in adendogram. ILS (Inverse Least Squares) A method of multivariatecalibration. ILS models assume the form y = Xb + e, where y is aproperty to be predicted, X is the measured response, b is the vector ofweights and e is the noise or error vector. K-means K-means is one ofthe algorithms in the larger class of cluster analysis. For K-means theuser inputs the number of expected classes and loadings are calculatedto group the scores into this many clusters. k-Nearest Neighbors (kNN)kNN is one of the algorithms in the larger class of cluster analysis.Supervised learning is required since each class must be labeled. A newsample is identified as the class that has k neighbors nearest theunknown, or the largest number of neighbors within the k nearestneighbors. LOESS (Locally Weighted The LOESS model performs a linearregression on Regression) points in the data set, weighted by a kernelcentered at x. The functional form of the kernel changes depending onthe sensitivity and span required for the given problem. MARS(Multivariate A multivariate non-parametric regression AdaptiveRegression procedure. The MARS procedure builds flexible Splines)regression models by fitting separate splines (or basis functions) todistinct intervals of the predictor variables. MLR (Multiple Linear Amethod of inverse least squares. The weights Regression) can becalculated by b = X⁺y, where X⁺ is a pseudo-inverse. The pseudo-inverseis defined (X^(t)X)⁻¹X^(t). Multi-Block PCA PCA models are developed foreach subsystem or unit operation. The outputs of the models forsubsystems are used as inputs for a single process model. Multi-Way PCAMulti-Way PCA is useful for batch processes or other transient data (awindow of data for a continuous process). Rather than the typical 2-dimensional array for PCA, multi-way PCA is a 3- dimensional array thatstill uses PCA for analysis. Specific algorithms include PARAFAC andTucker3. Neural Networks, Neural Neural Nets estimate relationshipsbetween one or Nets (NN) several input variables called independentvariables or descriptors (e.g. absorbance at different wavelengths) andone or several output variables called dependent variables or responses(e.g. concentration of a target analyte), without any a prioriassumption of a specific model form. Information in a NN is distributedamong multiple cells (nodes) and connections between the cells(weights). PCA (Principal Component PCA is one of the algorithms in thelarger class of Analysis), PA factor analysis. In PCA factors arecalculated by forming a linear combination of the sensor responses. PCAcan be used in an unsupervised mode. The coefficients (loadings) arecalculated based on capturing the greatest amount of variance subject toorthogonal constraints. PCR (Principal Components A method of inverseleast squares that is commonly Regression) used to deal withill-conditioned regression problems by regressing the property ofinterest (y) onto PCA scores. The pseudo-inverse is defined asP_(k)(T_(k) ^(t)T_(k))⁻¹T_(k) ^(t), P_(k) and T_(k) have the usualdefinitions for PCA—loadings and scores, respectively. PLS (PartialLeast Squares) A method of Inverse Least Squares (ILR) that addressesone of the shortcomings of Principal Components Regression (PCR). In PCRthe loadings are calculated without using the information contained inthe property of interest even when the data is available. PCR capturesmaximum variance of X (just like PCA), MLR achieves maximum correlationof X with y (at the expense of variance within x), and PLS maximized thecovariance between X and y. The pseudo- inverse is calculated byW_(k)(P_(k) ^(t)W_(k))⁻¹(T_(k) ^(t)T_(k))⁻¹T_(k) ^(t), where W isadditional set of weights to maintain orthogonality. PPR (ProjectionPursuit A multivariate non-parametric regression Regression) procedure.Projects the data onto a smaller number of dimensions and then allowsrotation to pursue — interesting features. RPR (Recursive Partitioning Amultivariate non-parametric regression Regression) procedure that wasdesigned to find local low- dimensional structure in functions thatshows high- dimensional global dependence. The output is a decision treeor dendogram. SIMCA (Soft Independent SIMCA considers each classseparately. For each Modeling of Class class separately a principalcomponent analysis is Analogy) performed which leads to a PC model foreach class (so-called disjoint class models). Supervised training isrequired for classification.

One multivariate technique listed in TABLE 10 is principal componentanalysis (PCA). PCA involves a procedure that transforms a number of(possibly) correlated variables into a (smaller) number of uncorrelatedvariables called principal components. PCA is included so that modelbuilders can perform multivariate statistical process control with asimple -technique that focuses on the process state. PCA is awell-documented method in literature for process control, and thetechniques for detecting anomalies are well tested.

For model building, inputs for PCA include sensor readings over time formultiple sensors arranged in a two-dimensional matrix. The number ofcolumns equals the number of sensors, and the number of rows equals thenumber of time stamps. Expected outputs for PCA include:

-   -   1. The number of PCs (Principal Components)    -   2. For each PC, a loading value for each sensor. The loadings        are saved in a two-dimensional matrix. The number of columns        equals the number of principal components, and the number of        rows equals the number of sensors.    -   3. Hotelling T² Control Limit    -   4. Q-Residual Control Limit

Depending on the number of PCs, one of the following charts will be thedefault. For one PC, a scores plot is the default having PC1 (PrincipalComponent 1) on the y-axis and time on the x-axis. A loadings plot mayalso be employed having PC1 on the y-axis and time on the x-axis. Fortwo PCs a scores plot is the default having PC2 on the y-axis and PC1 onthe x-axis. A loadings plot with the same axes may also be used. Forthree or more PCs, a scores plot is the default having PC3 on thez-axis, PC2 on the y-axis, and PC1 on the x-axis. A loadings plot withthe same axes may also be used. If there are more than three PCs, theuser should be given the option of selecting which PCs to display, andwhich of the three views to use.

Automatic alarms may be triggered under two conditions. A severity 3alarm is triggered, and text indicating “Control Limit Exceeded—T²”,when the condition Hotelling T² (when model is run)>Hotelling T² ControlLimit. A severity 4 alarm is triggered, and text indicating “ControlLimit Exceeded—Q”, when the condition: Q-Residual (when model isrun)>Q-Residual Control Limit.

For model monitoring using PCA, inputs include data for all “SensorsUsed” in the model at a given point in time, and a loading value foreach sensor for each principal component (based on model results).Expected outputs include scores for each principal component, hotellingT² at a given point in time, and Q-Residual at given point in time. Toplevel charts/plots used include a default display of Hotelling T² valueas a function of Time displayed using Hotelling T² vs. Time chart. Eachpoint represents a measure of deviation (Hotelling T²) from the model ata point in time. Points that are outside the expected control limitshould be highlighted. For Q-Residual value, the default display isQ-Residual value as a function of Time displayed using a Q-Residual vs.time chart. Each point represents a measure of deviation (Q-Residual)from the model at a point in time. Points that are outside the expectedcontrol limit should be highlighted.

Second level charts/plots used include:

-   -   1. From a point on the Hotelling T² as a function of Time chart,        a default display of the top 10 Sensors contributing to the        Hotelling T² value using a contribution plot. The sensors values        are sorted highest to lowest.    -   2. From a point on the Q-Residual as function of Time chart, a        default display of the top 10 Sensors contributing to the        Q-Residual value using a contribution plot. The sensors values        are sorted highest to lowest.

Third level charts/plots used include, from a sensor selected on eitherof the contribution plots in Level Two, a default display control chartfor sensor chosen. Begin plot, [n units in time] before the point intime selected in Level 2, and end the plot [n units in time] after thepoint selected in Level 2. Get n from the sensor's “Default Time Frame”in TABLE 2A).

Another multivariate technique listed in TABLE 10 is partial leastsquares (PLS). PLS is included so that model builders can developvirtual, inferential or soft sensors for processes. There are two mainreasons to use virtual sensors. Virtual sensors may be used to correlatecommonly measured process variables (e.g., pressure, temperature, flowrate) with infrequently measured lab results (e.g., density, pour point)so that the lab result can be approximated on-line, in real-time at thesame acquisition rate as the process variables. Virtual sensors may alsobe used to create a virtual redundant sensor by correlating themeasurements of many process variables with one other process variable.For instance, there is a detector at the end of an emissions stack thatmeasures the concentration of a specific gas being released to theenvironment. The EPA requires a redundant sensor for such cases and hasrecently accepted the results of a virtual redundant sensor instead of ahard redundant sensor.

For Model Building using PLS, inputs include sensor readings over timefor multiple sensors arranged in a two-dimensional matrix. The number ofcolumns equals the number of sensors, and the number of rows equals thenumber of time stamps. Another input is target property measurement overtime. Expected outputs from PLS Model Building include the number oflatent variables, the set of loadings (one per sensor per latentvariable), a standard error of prediction; a measurement of how good themodel was given the input data, and a Residual Control Limit. Top levelcharts/plots used include a Loadings Plot of latent variables. Aseverity 4 alarm may be triggered where Residual (when model isrun)>Residual Control Limit, and text indicating “Control LimitExceeded—PLS Residual” will be displayed.

For Model Monitoring using PLS, inputs include data for all “SensorsUsed” in the model at a given point in time, and loadings by sensor,with one loading per latent variable. Expected Outputs include predictedvirtual sensor (i.e., target property) value, and residual value(measure of the model validity for the input data). Top levelcharts/plots used include residual value as a function of Time displayedusing an x vs. y chart. Each point represents a measure of deviation(the Residual) from the model at a point in time. Points that areoutside the expected control limit should be highlighted. In a virtualsensor control chart. Each point represents the predicted value of thevirtual sensor at a point in time. Points that are outside the expectedcontrol limit should be highlighted. Second level charts/plots usedinclude from either plot a contribution plot in which each barrepresents an individual sensor. Either residual values or predictedvirtual sensor values can trigger alarms:

Another multivariate technique listed in TABLE 10 is Multi-block PCA.Multi-block PCA is included so that models can be built for individualunit operations (or sub-systems) during the evaluation period and theoutput of these models can then be used as inputs to an overall processmodel. Building an overall process model is a simpler process for themodel builder if there are existing models for unit operations. Thereare additional benefits to this technique. For example, the overallprocess model does not require every sensor in the plant to be an inputsince the models for unit operations determine the important variablesto be passed to the overall model; thus, the computation time is reducedby a factor approximately equal to the number of unit operations. Whenan anomaly is detected in the overall process model, the model can firstdetermine which unit operation(s) caused the fault and then determinewhich sensor(s) caused the disturbance.

Inputs during model building include sensor readings over time, virtualsensor readings over time, and outputs from other PCA models. Expectedoutputs for PCA include:

-   -   1. The number of PCs (Principal Components)    -   2. For each PC, a loading value for each sensor. The loadings        are saved in a two-dimensional matrix. The number of columns        equals the number of principal components, and the number of        rows equals the number of sensors.    -   3. Hotelling T² Control Limit    -   4. Q-Residual Control Limit

Depending on the number of PCs, one of the following charts will be thedefault. For one PC, a scores plot is the default having PC1 (PrincipalComponent 1) on the y-axis and time on the x-axis. A loadings plot mayalso be employed having PC1 on the y-axis and time on the x-axis. Fortwo PCs a scores plot is the default having PC2 on the y-axis and PC1 onthe x-axis. A loadings plot with the same axes may also be used. Forthree or more PCs, a scores plot is the default having PC3 on thez-axis, PC2 on the y-axis, and PC1 on the x-axis. A loadings plot withthe same axes may also be used. If there are more than three PCs, theuser should be given the option of selecting which PCs to display, andwhich of the three views to use.

Automatic alarms may be triggered under two conditions. A severity 3alarm is triggered, and text indicating “Control Limit Exceeded—T2”,when the condition Hotelling T² (when model is run)>Hotelling T² ControlLimit. A severity 4 alarm is triggered, and text indicating “ControlLimit Exceeded—Q”, when the condition: Q-Residual (when model isrun)>Q-Residual Control Limit.

Inputs for model monitoring utilizing Multi-block PCA include data forall “Sensors Used” in the model at a given point in time, data for allvirtual sensors used in the model at a given point in time, and outputsfrom other PCA models. Expected outputs from model monitoring includescores for each principal component, Hotelling T² at a point in time,and Q-Residual at a point in time. Values for hotelling T² andQ-Residual can trigger alarms.

The same charts/plots used on the top and second level as with PCA.Third level charts/plots are also the same as PCA, except if a sensorselected on either of the contribution plots in Level Two is:

-   -   1. An output from another PCA model, then display Hotelling T2        and Q-Residual as a function of time for that particular model.        Use the same hierarchy for PCA models as usual.    -   2. An output from a virtual sensor, then display the residual        value as a function of Time displayed using an x vs. y chart.        Each point represents a measure of deviation (the Residual) from        the model at a point in time. Points that are outside the        expected control limit should be highlighted. Use the same        hierarchy for PLS models as usual.

Another multivariate technique of TABLE 10 is Canonical DiscriminantAnalysis (CDA). CDA can perform two functions: identification ofanomalies, and data mining. There are other ways for identifyinganomalies, for example expert systems. However, the Software already hasCDA coded in multiple forms and should be easy to implement. CDA wouldno longer be required for process monitoring once an expert system is inplace.

CDA is a useful technique for data mining and provides one of thediscriminant algorithms for performing supervised analysis. The loadingsof a CDA may be vastly different than the loadings of a PCA model forthe same data set since a CDA model attempts to maximize the variancebetween classes. PCA calculates loadings by maximizing the variance-captured, regardless of its source. Note a class is simply a collectionof data that is given a label and is required for supervised training.For instance, the class names can be a condition (e.g., normal,start-up) or a recipe (e.g., HA-123, SBR-542) or any other collection ofdata that can be given a common label.

Inputs for model building using CDA include:

-   -   1. Sensor readings over time for multiple sensors arranged in a        two-dimensional matrix. The number of columns equals the number        of sensors, and the number of rows equals the number of time        stamps.    -   2. A label associated with each time stamp (or series of time        stamps) that properly identifies the condition of the process        during the time period (e.g., normal, start-up, shut-down,        idle).    -   3. One of the process conditions must be labeled ‘default’ state        for alarms. Typically, the class containing normal operating        conditions for a given product/recipe is the default condition.    -   4. Classification limit. The limit for probability that is used        to determine whether or not a given process state is a member of        one of the classes in the model.

Outputs expected from CDA include the number of PCs (PrincipalComponents), and for each PC, a loading value for each sensor. Theloadings are saved in a two-dimensional matrix. The number of columnsequals the number of principal components, and the number of rows equalsthe number of sensors.

The same top level charts/plots are used as in PCA model building.Automatic Alarms are triggered by the probability of the current statebeing part of the ‘default’ class. If the probability falls below acertain limit, then an alarm is sounded. Furthermore, if the probabilityis high for the current state as being part of another class, thenreport the identified class.

CDA can also be used for model monitoring and data mining. Inputs formodel monitoring include data for all “Sensors Used” in the model at agiven point in time, and also include loading value for each sensor foreach principal component (based on model results). The library includesstatistics regarding scores for each class in the model.

Expected outputs include an identifier such as one of the labels usedwhile building the model, and also include a measure of thelikelihood/probability that the identifier is correct. For data miningtop level charts/plots used are the same as CDA model building. CDAwould likely not utilize plots for real-time process monitoring. Forreal-time monitoring, CDA will be used to identify the state of theprocess or unit operation based on the results of underlying models. Theprobability of the current state being part of the ‘default’ class cantrigger an alarm. If the probability falls below a certain limit, thenan alarm is sounded. Furthermore, if the probability is high for thecurrent state as being part of another class, then report the identifiedclass.

Another multivariate approach of TABLE 10 is Multi-way PCA. Multi-wayPCA will be evaluated along with the components of SCREAM andcommercially available software when evaluating fault detectioncapabilities for process dynamics.

Multi-way PCA is a natural choice since PCA is already included,algorithms are available for evaluation in Matlab toolboxes, and thetechnique serves as a good benchmark when discussing benefits of otheralgorithms. There is one major difference between PCA and multi-way PCA.PCA does not account for the fact that the data was acquired in asequential manner. Multi-way PCA takes advantage of this information. Ifmulti-way PCA exhibits features during the evaluation period that thecomponents of SCREAM do not, then multi-way PCA would be evaluated forinclusion in the initial development phase. Specific algorithms alreadyexist for this calculation, including PARAFAC, Tucker3, tri-lineardecomposition, etc.

Inputs for multi-way PCA include sensor readings over-time for multiplesensors for multiple batches (or time windows in a continuous process)are arranged in a three-dimensional matrix. The number of columns equalsthe number of sensors, the number of rows equals the number of batches,and the depth of the array equals the number of time stamps. The outputsexpected, automatic alarms, and top, second, and third levelcharts/plots would be the same as for PCA model building.

For monitoring of a model using multi-way PCA, inputs include sensorreadings over time for multiple sensors for multiple batches (or timewindows in a continuous process) are arranged in a three-dimensionalmatrix. The number of columns equals the number of sensors, the numberof rows equals the number of batches, and the depth of the array equalsthe number of time stamps. Another input for multi-way PCA modelmonitoring is a loading value for each sensor for each principalcomponent (based on model results). The outputs expected, automaticalarms, and top, second, and third level charts/plots would be the sameas for PCA model monitoring.

TABLE 11 shows the SCREAM techniques supported by the Software.Initially the focus will be upon the pre-processing portion of the ModelFilter, coherence-based fault detection, and dynamical invariant anomalydetection. These three boxes will allow sufficient evaluation of theSCREAM system. Subsequently, the remaining SCREAM components will bedeveloped. This development phase will also include the other portionsof the Model Filter, if required—integration with models would be arequirement if the relationship requires more than just runningsimulation data through the algorithms before running real data. TABLE11 SCREAM TECHNIQUES SCREAM Technique Name Description Model FilterSeparates time-correlated sensor data (known physical (“Grey Box”)behavior, stationary components, linear components, non-linearcomponents, noise). Combines data components with physical or heuristicmodels of arbitrary quality. Symbolic Data Considers all discretesignals from the system. Detects Model and enumerates state mismatchesand explicit failures. Identifies operating mode of the system. Predictsstate of system components. Coherence Computes a single, complex,cross-signal invariant Based Fault (“Coherence Plot”) for eachsubsystem. Matches Detector invariant to mode-indexed invariantprediction. Identifies and quantifies deviations (single signaldepartures, multiple signal departures, known or novel events).Identifies return to expected behavior. Isolates deviation to sensors,sensor pairs, and timetags events. Dynamical Examines individual signals(either signals with low Invariant redundancy or signals identified byCoherence Anomaly Detector). Extracts invariant features from correctedDetector sensor data. Identifies and quantifies deviations (confirms oraugments cross-channel findings, classifies as known or novel events.Informed Studies the evolution of cross-channel behavior over theMaintenance medium- and long-term operation of the system. Grid (IMG)Prognostic Feature-based and Coherence-based trending to failure.Assessment Inclusion of physics models. Determination based onperformance characteristics and fused information. Capability to usefailure models or fault data. Predictive Combines numeric and symbolicresults into a unified Comparison result. Correlates detected eventswith predicted states to derive predicted failures and un-modeledevents. Processes explicit anomalies and correlates them to detectedevents.

The Model Filter SCREAM technique of TABLE 11 is used to compare thecurrent sensor measurements to the results of a theoretical (ornumerical) model. A difference is calculated for each sensor in themodel, and these differences are passed to the Dynamical InvariantAnomaly Detector along with all sensor responses.

Inputs during Model Building include sensor readings over time. Expectedoutputs during Model Building include sensor differences over time.Information saved with model includes the results for the theoreticalmodel, and the sensors used in the theoretical model. It is unlikelythat every sensor will be included in the theoretical model. Inputsduring Model Monitoring include sensor readings over time. Outputsexpected during Model Monitoring include sensor differences over time.

The Coherence-Based Fault Detector SCREAM technique of TABLE 11identifies single sensor faults (e.g., excessive noise, sensor drift,sensor failure) and multiple sensor anomalies (e.g., unexpectedfeedback, complex failures) by evaluating the correlation betweendifferent sensors within a subsystem. Separate models are built for eachunit operation or sub-system to reduce the needless complexity and sizeof a single process model.

Inputs during model building include a list of sensors to be modeled,sensor readings over time, a label for mode of operation (or class),such as steady-state, start-up, etc., and a definition of which of themodes of operation is the default. Expected outputs during modelbuilding include a window of time used in calculations, a statisticaldescription for the coherence for each sensor pair for process state,and a control limit for matrix norm for coherence difference plot. Toplevel charts/plots used include a coherence plot. An automatic alarm ofseverity 3 is triggered, and text is displayed stating “Control LimitExceeded—Coherence Miatrix Norm”, when the coherence matrix norm (whenmodel is run)>coherence matrix norm Control Limit.

For Model Monitoring using Coherence Based fault detection, inputsinclude data for all “Sensors Used” in the model at a given point intime and all prior times within the time window specified in the model,as well as a list of sensors to be modeled. The library includesstatistics regarding the coherence plots for each state/class. ExpectedOutputs include coherence for each sensor pair, a matrix norm forcoherence difference plot when using the default for the calculation,and identification of process state based on comparison with library ifmatrix norm is too large for default state. If matrix norm is too largefor all states in library, then expected output would be ‘unknownprocess state.’

Charts/plots used on the top-level include a default display of theCoherence Difference Matrix Norm as a function of Time displayed usingCoherence Difference Matrix Norm vs. Time chart. Each point represents ameasure of deviation (matrix norm) from the default process state.Points that are outside the expected control limit should behighlighted. Charts/plots used on the second level include a defaultdisplay of Coherence difference plot for the current process conditionsand the default process state. The coherence difference plot may be madefor current process conditions and the identified process state if aprocess state other than the default state was identified. Values of thecoherence difference Matrix Norm (using default process state tocalculate difference), can trigger alarms.

The Dynamical Invariant Anomaly Detector SCREAM technique of TABLE 11 isused to detect faults in single channels and is used to either confirmor augment the findings during coherence-based fault detection. Themethods used can detect a change in the underlying structure (e.g., achange in frequency) but cannot detect a change in operation (e.g., achange in amplitude).

An autoregressive model is built to capture linear dynamics. Theresiduals from this model are then modeled separately by (1) anartificial neural network to capture the nonlinear behavior of thedynamics and (2) the moments of the probability distribution to modelthe noise characteristics. A model should not be built for every sensorand should only be used for critical sensors. If all sensors aremodeled, then the rate of false alarms is not much smaller than currentlevels. Additionally, the computation time may be prohibitive.

Inputs for model building include sensor readings over time duringnormal operation. Expected Outputs from the model include:

-   -   1. window of time used in calculations, average and standard        deviation for each of the coefficients in the linear        autoregressive (AR) model for each sensor;    -   2. control limits for AR coefficient difference;    -   3. average and standard deviation for each of the coefficients        in the neural network (NN) model for each sensor;    -   4. control limits for NN coefficient difference;    -   5. average and standard deviation for each of the probability        distributions (PD) for each sensor; and    -   6. control limits for PD difference.

An alarm of severity 3 may automatically be triggered under a number ofconditions. For example, when the AR coefficient difference (when modelis run)>AR coefficient difference Upper Control Limit, or AR coefficientdifference (when model is run)<AR coefficient difference Lower ControlLimit, a message is displayed stating that “Control LimitExceeded—sensor name, linear dynamics”. Similarly, when the NNcoefficient difference (when model is run)>NN coefficient differenceUpper Control Limit, or NN coefficient difference (when model is run)<NNcoefficient difference Lower Control Limit, a message is displayedstating that “Control Limit Exceeded—sensor name, non-linear dynamics”.Finally, when the PD difference (when model is run)>PD difference UpperControl Limit, or PD coefficient difference (when model is run)<PDdifference Lower Control Limit, a message is displayed stating that“Control Limit Exceeded—sensor name, noise characteristics”.

For model monitoring using Dynamical Invariant Anomaly Detector, inputsinclude sensor readings over time during normal operation, the window oftime used in calculations, and the expected process state (Default:normal; phase 2: based on symbolic data). The library includes averagevalues and control limits for autoregressive (AR) coefficient differencefor each coefficient for all defined process states, average values andcontrol limits for neural network (NN) coefficient difference for eachcoefficient for all defined process states and average values andcontrol limits for probability distribution (PD) difference for eachdistribution for all defined process states.

Expected Outputs of the model include current data such as ARcoefficient difference, NN coefficients, and PD values, and also thedifference between current and expected values for AR, NN, and PD.Values of AR coefficient difference, NN coefficient difference, and PDdifference can trigger alarms. Top level charts/plots used areuser-selectable but do not include a default since every sensor willhave the following charts:

-   -   1. control chart for AR coefficient difference;    -   2. control chart for NN coefficient difference; and    -   3. control chart for PD difference.

Glossary

The following represents a concise explanation of certain termsreferenced in the above discussion. This listing is for informationalpurposes only, and is not intended to define or otherwise limit theterms. Other meanings of the listed terms may be understood.

Bluetooth: A set of radio wave communication protocols and standardsthat enable low-cost, high-speed communication among devices that arewithin 10 meters (approximately 33 feet) of each other (this distancecan be increased to 100 meters with amplifiers or increasing thetransmit power).

Foundation Fieldbus: A bi-directional communications protocol used forcommunications among field instrumentation and control systems.Foundation Fieldbus is the only digital fieldbus protocol developed tomeet the ISA's SP50 requirements, and is the only protocol that meetsstringent, mission-critical demands for intrinsic safety and use inhazardous areas, volatile processes and difficult regulatoryenvironments.

GUI: Graphical User Interface.

HMI (Human Machine Interface): Also known as man machine interface.Systems for operating plants, monitoring processes and backing up datain industrial manufacturing processes. Smaller packaging machines havesimple control units while powerful visualization systems based onindustrial PCs are often used in complex packaging lines. Such systemsdisplay the operating processes in a machine as flow diagrams and allowmore transparency in their monitoring. Important operational data arerecorded and graphically displayed. If something is not runningproperly, an alarm is generated immediately.

JPL (Jet Propulsion Laboratory): Managed for NASA by the CaliforniaInstitute of Technology, the Jet Propulsion Laboratory is the lead U.S.center for robotic exploration of the solar system. In addition to itswork for NASA, JPL conducts tasks for a variety of other federalagencies. JPL also manages the worldwide Deep Space Network, whichcommunicates with spacecraft and Conducts scientific investigations fromits complexes in California's Mojave Desert near Goldstone; near Madrid,Spain; and near Canberra, Australia.

OPC (OLE for Process Control): A communication standard based on OLE(Object Linking & Embedding) and COM (Component Object Model) technologythat forms the new means of exchanging information between MS Windowsapplications. It offers interoperability between the control, command,supervision applications, the industrial equipment (PLCs, sensors,actuators) and the office management applications. OPC defines standardobjects, methods and properties built on the COM concept to allow realtime data servers like DCS, PLC and field equipment to communicate theirdata to OPC clients.

PLC (Programmable Logic Controller): A device that can be programmed toreact to input signals. Modern day PLCs are sophisticated enough toperform any control task. PLCs are rugged, reliable, and easy toprogram. They are economically competitive with other control methodsand have replaced conventional hard-wired relay and timer panels in manyapplications. PLCs can stand alone, be networked together, or networkedto an Operator Interface or SCADA system.

Q (Q-Residual): A measure of deviation from a model where the deviationis outside the model. This measurement is referred to as Q or Q-Residualfor PCA. For PLS, it is called Residual.

SCADA (Supervisory Control and Data Acquisition): Contains components ofcontrol, analysis, monitoring, storage and management of the informationflow between the systems at the field level and the control level of acompany. This ensures that the decentralized I/O modules and the machinecontrollers are linked to the office computers on the control level.

SCREAM (System Coherence Rendering Exception Analysis for Maintenance):A collection of models based on technology developed at JPL that provideintelligence for system self-analysis. Originally called BEAM(Beacon-Based Exception Analysis for Multimissions) at JPL.

SPC: Statistical Process Control.

T² (Hotelling T²): A measure of deviation from a model where thedeviation is within the model.

Virtual Sensor: A collection of sensors, often used to measure a singleunit operation, that can be treated as a single unit (e.g., the 32sensors in the Cyranose 320). Individual sensors in the virtual sensorare given a weighting, and a resulting score is calculated. A virtualsensor may be treated like a regular sensor in a model.

Again, it is emphasized that the above-listed concise explanation ofterms is for informational purposes only and is not intended to limit orotherwise define the term for purposes of this application or the claimsset forth herein. Other meanings of the listed terms may be understood.

It is understood that the examples and embodiments described herein arefor illustrative purposes only and that various modifications or changesin light thereof will be suggested to persons skilled in the art and areto be included within the spirit and purview of this application andscope of the appended claims. All publications, patents, and patentapplications cited herein are hereby incorporated by reference for allpurposes in their entirety.

1-62. (canceled)
 63. An appended diagnostic system comprising: aplurality of sensors; a networking module for connecting said pluralityof sensors with a pre-existing networking module of a pre-existingmonitoring system; an integration module for integrating sensor datafrom said plurality of sensors with data from pre-existing sensors, toform integrated data, wherein said pre-existing sensors are coupled withsaid pre-existing monitoring system; and a preprocessing module forpreprocessing said integrated data for further processing by aprocessing module.
 64. The system of claim 63 wherein said plurality ofsensors comprises chemical sensors.
 65. The system of claim 63 whereinsaid plurality of sensors comprises thermal sensors for thermaldetection.
 66. The system of claim 63 wherein said plurality of sensorscomprises mechanical sensors.
 67. The system of claim 63 wherein saidplurality of sensors comprises radiation sensors.
 68. The system ofclaim 63 wherein said plurality of sensors comprises biological sensors.69. The system of claim 63 further comprising a processing module,wherein said processing module comprises: a storage module for storing amodel of a phenomenon; an application module for applying said model tosaid integrated data; and a generation module for generating adescriptor of a state of a phenomenon using said storage and saidapplication modules.
 70. The system of claim 69 further comprising amodel generation module for generating said model of a phenomenon. 71.The system of claim 70 wherein said model generation module generates amodel derived from fundamental thermodynamic laws.
 72. The system ofclaim 70 wherein said model generation module comprises a neural networkanalysis module.
 73. The system of claim 63 wherein said plurality ofsensors are wireless sensors configured to communicate with saidnetworking module via a communication mode selected from the groupconsisting of infrared communications, radiofrequency communications,and combinations thereof.
 74. The system of claim 63 wherein saidplurality of sensors are non-permanent sensors.
 75. The system of claim63 further comprising a processing module, wherein said processingmodule comprises a module for transmitting a portion of said integrateddata to a data interpretation system.
 76. The system of claim 63 furthercomprising a processing module, wherein said processing modules comprisea diagnostic module.
 77. The system of claim 76 wherein said diagnosticmodule comprises modules for diagnosing the operational state of ahydrocarbon processing equipment.
 78. The system of claim 63 furthercomprising a processing module, wherein said processing module furthercomprises modules for providing a notification regarding an occurrenceof an event.
 79. The system of claim 63 further comprising a processingmodule, wherein said processing module further comprises modules forinitiating follow-on actions.
 80. The system of claim 79 wherein saidfollow-on actions includes correction means responsive to an event. 81.The system of claim 63 wherein said networking module further comprises:a short-range transceiver node, configured to be connected with saidplurality of sensors; a local hub, connected with said short rangetransceiver node; and a long-range transceiver hub connected with saidpre-existing monitoring system, wherein said long-range transceiver hubis configured to exchange data with said local hub.
 82. An appendeddiagnostic system comprising: a plurality of sensors in which each ofsaid plurality of sensors is either a chemical sensor, a biologicalsensor, or a radiological sensor; a networking module for connectingsaid plurality of sensors with a pre-existing networking module of apre-existing monitoring system having a plurality of pre-existingsensors; and a preprocessing module for preprocessing data obtained fromsaid plurality of sensors and data obtained from said plurality ofpre-existing sensors, for further processing by a processing module.